[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: RE: Re: [DESIGN] Aliases? (Was: RE: Re: I, too, miss tags.)

From: Thompson, Graeme (AELE) <Graeme.Thompson_at_smiths-aerospace.com>
Date: 2006-02-28 16:35:40 CET

> Well, I've suggested merge-tracking (I think tagging each
> merge, as you
> suggested above, is a remarkable kludge around the lack of a way to
> track revision numbers) and a way to link in to the issue tracker
> (ISSUE_1423_FIX, for instance).

And of what use is linking to your issue tracker in this fashion, you
can put the list of issues fixed in the commit comment, but really what
you will only ever want to know is what revision was this issue fixed
in, which is linking from the issue tracker to the subversion
repository, where stating fixed in trunk revision xxx gives you an
explicit way of getting to a revision of a project.

On a more general note, this is getting a little longwinded, when IMHO
there has not been any good argument for aliasing a number to a text
string other than "I don't like using a number to define a repository
state". If you are all so desperate to save typing, why not simply
create an svn wrapper script that allows you to macro a revision number
and repository path to an "easy to remember" text string. Thus you could

my_svn "My easy to remember string"

To do a get on a predefined revision.


Oh well - here is my contribution to keep this going a bit longer ;)

The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 28 17:53:05 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.