> Subversion currently has:
>
> To create a new tag:
>
> svn cp $R/$P/{trunk,tags/$T} -m "Creating tag $T"
I think illustrates the problem. That is a very cumbersome line to type just to tag a version for future reference. It's error prone and requires me to know (or remember) a lot about the repository. I work on a lot of different projects connected to different servers using two different access methods. Each time I want to quickly create a tag (like when I send a version to testing), it's a pain, and when something is a pain to do, people stop doing it.
On top of that, we are on Windows, so doing things like {trunk,tags/$T} won't work, we're forced to type the whole line (please do not bring up cygwin, because that is missing the point).
Everyone that is asking for "tags" understands that subverison can already do what they want, but what we're looking for is a easier more intuitive way to do it.
When I want to update my WC, I just type:
svn update
Simple and I don't have to remember paths to repositories even the access methods. All I want is something that is that simple and easy to remember to apply a quick tag (or revision # alias).
I am all in favor of finding the correct solution to this and not just a kludge, but every time I have to create a whole new branch of my project just to tag a simple version I send to test so I remember, I feel like that's a kludge.
Ron
Ryan Schmidt wrote:
>
> On Feb 24, 2006, at 18:11, robert@infotility.com wrote:
>
>> Since we know already that symbolic aliases are useful
>> (HEAD, BASE, etc) why not set up a mechanism to allow
>> users to make new ones?
>>
>> Various correspondents have suggested workarounds or
>> hacks of various kinds. Thanks guys, but if there's
>> evidence that there is widespread desire for this feature
>> (namely that it has been solved multiple times by
>> multiple persons) why not just build it into the standard release?
>
>
> I for one just don't understand yet what functionality is being gained.
>
>
> Given a project named $P and a repository whose root is $R, and a
> standard trunk/branches/tags structure in the project, and a tag named $T,
>
>
> Subversion currently has:
>
> To create a new tag:
>
> svn cp $R/$P/{trunk,tags/$T} -m "Creating tag $T"
>
> To replace an existing tag:
>
> svn rm $R/$P/tags/$T -m "Removing tag $T"
> svn cp $R/$P/{trunk,tags/$T} -m "Recreating tag $T"
>
> To check out the tag:
>
> svn co $R/$P/tags/$T
>
> To get a log of the tag:
>
> svn log $R/$P/tags/$T
>
>
> What's being proposed seems to be:
>
> To create a new tag:
>
> svn alias [-r HEAD] $T $R/$P/trunk
>
> To replace an existing tag:
>
> svn alias -force [-r HEAD] $T $R/$P/trunk
>
> To check out the tag:
>
> svn co -r $T $R/$P/trunk
>
> To get a log of the tag:
>
> svn log -r $T:0 $R/$P/trunk
>
>
> Is it just this alternate syntax that's desired, or is there some
> additional functionality that's gained over Subversion's existing
> tagging method that I'm just not seeing at the moment?
>
> The idea of CVS-like tags, or revision aliases, or revision labels, or
> symbolic names for revisions, has come up on this mailing list many,
> many times before (you can search the list archives for some of those
> terms if you're interested). But I don't think anyone has so far
> succeeded in making a compelling enough case that the benefit of having
> this feature would outweigh the considerable development effort needed
> to implement it.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Feb 25 17:10:16 2006