On 6/8/06, Molle Bestefich <molle.bestefich@gmail.com> wrote:
> Stefan Küng wrote:
> > And since you should not commit to a tag, we show the warning.
>
> Not true per se.
> You can copy /trunk to /tags/xyz in your WC and then commit that,
> which is just as good as a server-side copy.
>
Many of us have working copies far to large to checkout the base of
the repository, especially after creating numerous tags and branches.
> It has advantages over a server-side copy, for example if you have
> fixed version numbers you can modify those before commit.
>
Shouldn't this have been already modified and committed before the tag
is created?
> Commit to a tag can also be useful for hotfixes, makes it easy to see
> which hotfixes are/should be applied to which version of your product.
>
This goes against what a tag is supposed to be. If you start
modifying it with hotfixes then it is really conceptually a branch,
not a tag. Normal procedure I use is to copy the tag to a branch if
I'm going to start modifying it. If you're not goign to use tags as
just simple names mapping to a specific revision, then why don't you
just use branches? Then you won't see this warning.
Since subversion doesn't really have any specific concept of tags and
branches, just copies of directories, you can really name all this
stuff whatever you want and use it however you want. Many of us are
however following stricter definitions of what a tag and branch are,
and greatly appreciate the warning. Instead of the dialog being
removed, maybe a checkbox could be added to supress the dialog from
coming up in the future?
- Jody
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Jun 8 16:04:02 2006