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

To cut this ongoing discussion short: Is there anything that revision
aliases would allow you to to that the current tagging mechanism does
not allow you to do?

Note: You can currently tag the whole repository, for every definition
of "whole repository" that matters, by setting up your repository like
this:
   /tags
   /whole_repository
     /project1
       /trunk
       /branches
     /project2
       /trunk
       /branches

Note: You can (and should, in the absence of built-in merge tracking)
keep track of merge points using the current tagging mechanism.

If there is anything that revision aliases allow you to do that cheap
copies don't allow, I would love to hear it. If there is nothing, then
the only benefit of revision aliases is syntax sugar. In that case, the
problem can be solved quite elegantly by writing a tag-aware subversion
client, without changing anything on the server side.

-- 
Rainer Deyke - rainerd_at_eldwood.com - http://eldwood.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org