Den tors 11 mars 2021 kl 19:26 skrev TortoiseSVN <
[email protected]>:
> 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
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tortoisesvn/CAMHy98OpV%2BZjP1jgBwfBekgD5UuUb7ME49E5NR--p2E36Wfc2A%40mail.gmail.com.
