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

Gale, David wrote:
> Rainer Deyke wrote:
>>Note: You can (and should, in the absence of built-in merge tracking)
>>keep track of merge points using the current tagging mechanism.
>
>
> Or in the absence of a good way to record the last merged revision,
> which revision aliases would give.

Once again I ask, what actual technical benefits would you gain by
recording the revision instead of using a cheap copy? I can think of
many benefits of using cheap copies instead of recording the revision:

1. You can have a mixed revision merge point if you decide to merge just
part of the branch to the trunk.

2. You have a hierarchical naming for merge point to match the
hierarchical naming of branches, thereby keeping the repository clean
when there are thousands of private branches.

Given those benefits and the absence of any drawback, I would strongly
recommend using cheap copies instead of revision aliases for merge
points, even if both were available.

-- 
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