Labanca, Rick wrote:
> My original use for ... Let's call it a revision alias... Is to keep
> track of merge repeats. I slide a tag in the trunk each time I merge
> from it. It's not an indicator of a copy of anything in the trunk, or
> even anything remotely buildable. It's just an alias for a point in time
> that developers can read and use for that purpose.
>
> In other words, making a copy from my sliding tag/alias wouldn't be
> legitamate code, therefore the copy in subversion is a bit odd to have
> around for this purpose.
How about simply checking in a file called "revision-alias" that contains
the revision number of the last merge? Every time you want to "slide"
your tag, edit the file and recommit. Or, store this info in a property.
E.g., this discussion reminds me of the UNIX principle that tools
should "do one thing and do it well" and that complexity should come
from combining simple tools rather than having tools themselves be
complicated.
To me subversion is a great tool that does one thing well, i.e.,
maintain an unforgetting file system with meta-data properties.
There are lots of other things people want to do with it, but IMHO
most of these can (and should) be done by writing other tools or
wrappers (e.g., my little 'svnmerge' script (see previous post)).
Of course, it's also nice to come to some concensus on what the right
toolset is so there are zillions of them all different..
-Archie
__________________________________________________________________________
Archie Cobbs * CTO, Awarix * http://www.awarix.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 29 17:00:31 2004