Is there a way to disable ONLY the commit warning for tags?

[Thorsten Schöning]

Hi all,

I'm using tags to deploy/maintain web sites for customers, while those
customers are allowed to still change things in those tags. It's
mostly only about very tag-specific things like e.g. configs.

Many customers don't make such things too often and are then a little
bit scared about the warning TSVN provides by default. they call me, I
tell them to ignore that and sometimes explain the reasons one more
time, until the next time in a few months. :-)

I've already read that this warning can be "disabled" by removing
classification patterns in the settings of the revision graph:

https://groups.google.com/g/tortoisesvn-dev/c/Bp_M7FK4BE0/m/vZxECV6Kb5cJ

But is there a way to KEEP TSVN knowing about tags etc., while ONLY
disabling that special commit warning?

The commit warning is not strictly associated with the revision graph
as well, but depends on that setting. So I wonder which other useful
functions one loses when changing that setting onyl to disable the
commit warning.

Is there some advanced setting targeting that warning I'm missing?

Thanks!

Mit freundlichen Grüßen

Thorsten Schöning

--
AM-SoFT IT-Service - Bitstore Hameln GmbH i.G.
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister für IT und TK

E-Mail: Thorsten....@AM-SoFT.de
Web: http://www.AM-SoFT.de/

Tel: 05151- 9468- 0
Tel: 05151- 9468-55
Fax: 05151- 9468-88
Mobil: 0178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH i.G., Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB neu - Geschäftsführer: Janine Galonska


Für Rückfragen stehe ich Ihnen sehr gerne zur Verfügung.

Mit freundlichen Grüßen

Thorsten Schöning


Tel: 05151 9468 0
Fax: 05151 9468 88
Mobil:
Webseite: https://www.am-soft.de

AM-Soft IT-Service - Bitstore Hameln GmbH i.G. ist ein Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister für IT und TK

AM-Soft IT-Service - Bitstore Hameln GmbH i.G.
Brandenburger Str. 7c
31789 Hameln
Tel: 05151 9468 0

Bitstore IT-Consulting GmbH
Zentrale - Berlin Lichtenberg
Frankfurter Allee 285
10317 Berlin
Tel: 030 453 087 80

CBS IT-Service - Bitstore Kaulsdorf UG
Tel: 030 453 087 880 1

Büro Dallgow-Döberitz
Tel: 03322 507 020

Büro Kloster Lehnin
Tel: 033207 566 530

PCE IT-Service - Bitstore Darmstadt UG
Darmstadt
Tel: 06151 392 973 0

Büro Neuruppin
Tel: 033932 606 090

ACI EDV Systemhaus Dresden GmbH
Dresden
Tel: 0351 254 410

Das Systemhaus - Bitstore Magdeburg GmbH
Magdeburg
Tel: 0391 636 651 0

Allerdata.IT - Bitstore Wittenberg GmbH
Wittenberg
Tel: 03491 876 735 7

Büro Liebenwalde
Tel: 033054 810 00

HSA - das Büro - Bitstore Altenburg UG
Altenburg
Tel: 0344 784 390 97

Bitstore IT – Consulting GmbH
NL Piesteritz
Piesteritz
Tel: 03491 644 868 6

Solltec IT-Services - Bitstore Braunschweig UG
Braunschweig
Tel: 0531 206 068 0

MF Computer Service - Bitstore Gütersloh GmbH
Gütersloh
Tel: 05245 920 809 3

Firmensitz: AM-Soft IT-Service - Bitstore Hameln GmbH i.G. , Brandenburger Str. 7c , 31789 Hameln
Geschäftsführer Janine Galonska

[Niemann, Hartmut]

Hi Thorsten!

If I recall correctly, the directory name "tags" is pure convention, and the warnings come from the directory name alone.

If you rename the directory to "releases" or something else, the problem should be gone, shouldn't it?
(And - as the subversion use case standard of "tagging" is understood them to be immutable, using a different name would be a good idea anyway.)

Hartmut

-----Ursprüngliche Nachricht-----
Von: TortoiseSVN <torto...@googlegroups.com>
Gesendet: Donnerstag, 11. März 2021 14:17
An: TortoiseSVN <torto...@googlegroups.com>
Betreff: Is there a way to disable ONLY the commit warning for tags?

Hi all,

I'm using tags to deploy/maintain web sites for customers, while those customers are allowed to still change things in those tags. It's mostly only about very tag-specific things like e.g. configs.

Many customers don't make such things too often and are then a little bit scared about the warning TSVN provides by default. they call me, I tell them to ignore that and sometimes explain the reasons one more time, until the next time in a few months. :-)

I've already read that this warning can be "disabled" by removing classification patterns in the settings of the revision graph:

https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fg%2Ftortoisesvn-dev%2Fc%2FBp_M7FK4BE0%2Fm%2FvZxECV6Kb5cJ&amp;data=04%7C01%7Chartmut.niemann%40siemens.com%7C357c951c085e40ac705a08d8e49009dd%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637510654572657014%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=hpdzcMdDrevRub7dwn0HAAJgkCpsHKQCuRCrCx%2Fl50k%3D&amp;reserved=0

But is there a way to KEEP TSVN knowing about tags etc., while ONLY disabling that special commit warning?

The commit warning is not strictly associated with the revision graph as well, but depends on that setting. So I wonder which other useful functions one loses when changing that setting onyl to disable the commit warning.

Is there some advanced setting targeting that warning I'm missing?

Thanks!

Mit freundlichen Grüßen

Thorsten Schöning

--
AM-SoFT IT-Service - Bitstore Hameln GmbH i.G.
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister für IT und TK

E-Mail: Thorsten....@AM-SoFT.de

Web: https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.am-soft.de%2F&amp;data=04%7C01%7Chartmut.niemann%40siemens.com%7C357c951c085e40ac705a08d8e49009dd%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637510654572657014%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=CepumLEuVF9knlsk7%2BlzJeJ3oDdMVA86wSoWpg%2FU9bA%3D&amp;reserved=0

Tel: 05151- 9468- 0
Tel: 05151- 9468-55
Fax: 05151- 9468-88
Mobil: 0178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH i.G., Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB neu - Geschäftsführer: Janine Galonska


Für Rückfragen stehe ich Ihnen sehr gerne zur Verfügung.

Mit freundlichen Grüßen

Thorsten Schöning


Tel: 05151 9468 0
Fax: 05151 9468 88
Mobil:

Webseite: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.am-soft.de%2F&amp;data=04%7C01%7Chartmut.niemann%40siemens.com%7C357c951c085e40ac705a08d8e49009dd%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637510654572657014%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=ckVUR5qPX5Rsf%2FRv7keIW9ok6VB36XejVS9RrPmDWOg%3D&amp;reserved=0

Bitstore IT - Consulting GmbH

NL Piesteritz
Piesteritz
Tel: 03491 644 868 6

Solltec IT-Services - Bitstore Braunschweig UG Braunschweig
Tel: 0531 206 068 0

MF Computer Service - Bitstore Gütersloh GmbH Gütersloh
Tel: 05245 920 809 3

Firmensitz: AM-Soft IT-Service - Bitstore Hameln GmbH i.G. , Brandenburger Str. 7c , 31789 Hameln Geschäftsführer Janine Galonska

--
You received this message because you are subscribed to the Google Groups "TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn...@googlegroups.com.
To view this discussion on the web visit https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Ftortoisesvn%2F1434069687.20210311141724%2540am-soft.de&amp;data=04%7C01%7Chartmut.niemann%40siemens.com%7C357c951c085e40ac705a08d8e49009dd%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637510654572657014%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=Y8oR44L%2BbjRyhj%2Be031bbQ7zJReWXFWD1lmc9sxahY8%3D&amp;reserved=0.

[Daniel Sahlberg]

Den tors 11 mars 2021 kl 14:17 skrev TortoiseSVN <torto...@googlegroups.com>:

Hi all,

I'm using tags to deploy/maintain web sites for customers, while those
customers are allowed to still change things in those tags. It's
mostly only about very tag-specific things like e.g. configs.

Many customers don't make such things too often and are then a little
bit scared about the warning TSVN provides by default. they call me, I
tell them to ignore that and sometimes explain the reasons one more
time, until the next time in a few months. :-)

I've already read that this warning can be "disabled" by removing
classification patterns in the settings of the revision graph:

https://groups.google.com/g/tortoisesvn-dev/c/Bp_M7FK4BE0/m/vZxECV6Kb5cJ

But is there a way to KEEP TSVN knowing about tags etc., while ONLY
disabling that special commit warning?

The commit warning is not strictly associated with the revision graph
as well, but depends on that setting. So I wonder which other useful
functions one loses when changing that setting onyl to disable the
commit warning.

Is there some advanced setting targeting that warning I'm missing?

Quickly checking the code (IsCommittingToTag in SVNProgessDlg.cpp) this seems to be the relevant setting.

Since this setting must be configured on every computer running TSVN you will probably receive the same amount of support calls to configure this as you are getting today.

Is it possible for you to switch nomenclature and call it "branch" instead? A "tag" is usually supposed to point to a fixed point in time ("the source as it was in version 1.2.3.4") and for this reason you are not supposed to commit to the tag.

--
You received this message because you are subscribed to the Google Groups "TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/1434069687.20210311141724%40am-soft.de.

[Thorsten Schöning]

Guten Tag TortoiseSVN,
am Donnerstag, 11. März 2021 um 15:41 schrieben Sie:

> Is it possible for you to switch nomenclature and call it "branch" instead?

Of course it's possible to restructure the repo and invent some
different naming scheme... But doesn't make much sense in my case. :-)
I'll just keep telling users once in a while to ignore that message or
consider using the available setting then. An advanced one disabling
the message only would really make sense here, though.

> A "tag" is usually supposed to point to a fixed point in time ("the source
> as it was in version 1.2.3.4") and for this reason you are not supposed to
> commit to the tag.

Which is a convention only, using tags for deployed software makes
sense as well and keeps branches for real development work. Deployed
software can be reconfigured while the software itself doesn't change.

[Daniel Sahlberg]

Den tors 11 mars 2021 kl 19:26 skrev TortoiseSVN <torto...@googlegroups.com>:

Guten Tag TortoiseSVN,
am Donnerstag, 11. März 2021 um 15:41 schrieben Sie:

> Is it possible for you to switch nomenclature and call it "branch" instead?

Of course it's possible to restructure the repo and invent some
different naming scheme... But doesn't make much sense in my case. :-)
I'll just keep telling users once in a while to ignore that message or
consider using the available setting then. An advanced one disabling
the message only would really make sense here, though.

You would still have to help the users to configure this setting. In which case it probably doesn't make much difference compared to configuring it under "Revision Graph"?

> A "tag" is usually supposed to point to a fixed point in time ("the source
> as it was in version 1.2.3.4") and for this reason you are not supposed to
> commit to the tag.

Which is a convention only, using tags for deployed software makes
sense as well and keeps branches for real development work. Deployed
software can be reconfigured while the software itself doesn't change.

Sure. This is where Subversion's flexibility in having "tags" and "branches" as regular directories only identified by a convention in the naming make things difficult. If it was a tag in another VCS then you might not be able to modify the content at all (and be forced to use their notion of a branch, or have completely separate repositories). TortoiseSVN is just trying to help you not break the convention of committing to a tag.

It is fairly well described in the help file:

[[[
Classification Patterns
The revision graph attempts to show a clearer picture of your repository structure by distinguishing between trunk, branches and tags. As there is no such classification built into Subversion, this information is extracted from the path names. The default settings assume that you use the conventional English names as suggested in the Subversion documentation, but of course your usage may vary.
Specify the patterns used to recognise these paths in the three boxes provided. The patterns will be matched case-insensitively, but you must specify them in lower case. Wild cards * and ? will work as usual, and you can use ; to separate multiple patterns. Do not include any extra white space as it will be included in the matching specification.

Commit tag detection
Please note that these patterns are also used to detect commits to a tag, not just for the revision graph.

]]]

Kind regards,

Daniel Sahlberg