Stefan Küng wrote:
> Rainer Müller wrote:
>> What about to default it to tags/ and make a new tsvn:tags_dir
>> property which
>> can be set to any pattern? If the property is not available it uses
>> tags/ but if
>> it is specified it uses that value.
> The idea of using tsvn: properties is not bad. But they only work if you
> have a working copy!
> Question: those of you who use the tsvn: properties (e.g.
> tsvn:logminsize or tsvn:projectlanguage), do you have set those on the
> branch/tags dir too or just on the /trunk folders? Because I think most
> people only set them on trunk and completely forget about branches/tags.
What are we trying to provide protection against? I think it is mainly
against someone switching their WC to a tag, then forgetting they have
done that and making changes which they commit to the tag instead of
trunk. So this is really only important if you _do_ have a WC.
Also, if you apply the property to trunk, when you create the tag the
property will be copied there as well. The trick is in deciding how to
use the tag. Maybe the simplest way is just to mimic what we already
tsvn:commitwarning = /release/
will generate a warning if you try to commit to a path which contains
It would be nice if you could specify multiple paths in the property,
newline separated, as for the ignore property.
tsvn:commitwarning = /tags/
To make this work in practice, the end user has to make sure the
property is set on the lowest level that tags will be created from, but
that is true of all TSVN properties.
Should this mechanism be in addition to existing hard coded protection
of /tags/, or should it replace that? If we replace, then existing
working copies will lose that protection until they add the new property.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Aug 30 11:41:40 2005