Yes -- once again, others seem better at explaining my use cases :)
>It would be up to the user to know which directory tree that the alias applies to. Kind of like how svnmerge.py requires that you know which top level dir contains the merge properties. =)
>
>The benefit would be in being able to:
> svn co -r REL.1.0.0 svn://url/trunk
> svn log -r REL.2.1.3 svn://url/trunk
> svn co -r LOGGING_1.0.0 svn://url/logging/trunk_at_LOGGING_1.0.0 (Peg revision)
>
>My inner ClearCase junkie is starting to see some usefulness in 'svn alias' as a way to do an in-place tag.
>
That's why I called it the poor man's tag :)
(And sorry about the msg format -- I use plain vanilla Thunderbird)
Cheers.
Reedick, Andrew wrote:
>>From: Bicking, David (HHoldings, IT) [mailto:David.Bicking_at_thehart
>>ford.com]
>>Sent: Wednesday, February 20, 2008 3:33 PM
>>To: OS
>>Cc: Reedick, Andrew; users_at_subversion.tigris.org
>>Subject: RE: feature request: svn revision alias
>>
>>How would you name a revision, knowing that it applies to the whole
>>repository, in such a way that it offers any kind of meaning? The
>>name "V3.14_baselevel3" appears to identify a particular branch of
>>a particular project. To me, this is adding confusion, because
>>that revision is global and might apply to
>>"V7.24.032_tertiarylevel1" on another project. So, once more, what
>>can the alias tell you that has more (and concise) meaning than the
>>revision number given its global nature?
>>
>>
>
>
>It would be up to the user to know which directory tree that the alias applies to. Kind of like how svnmerge.py requires that you know which top level dir contains the merge properties. =)
>
>The benefit would be in being able to:
> svn co -r REL.1.0.0 svn://url/trunk
> svn log -r REL.2.1.3 svn://url/trunk
> svn co -r LOGGING_1.0.0 svn://url/logging/trunk_at_LOGGING_1.0.0 (Peg revision)
>
>My inner ClearCase junkie is starting to see some usefulness in 'svn alias' as a way to do an in-place tag.
>
>
>Even better, if the alias also saved the associated URL:
> svn alias -r 1234 LOGGING.1.0.0 svn://repos/logging/trunk
>then you could have commands like:
> svn co LOGGING.1.0.0
> svn log LOGGING.1.0.0
> svn copy LOGGING.1.0.0 svn://server/logging/branches/rel.2.0
>which would mostly mimic the in-place tagging of traditional systems. However, you wouldn't be able to move tags on individual files.
>
>
>In either case, you would need the ability to lock down aliases to prevent idiots, the well-intentioned, and managers from changing or destroying an important alias.
>
>
>
>
>
>
>>(and I guess you can't send ASCII posts -too bad)
>>
>>
>
><tinfoil_hat>
>I'm pretty sure that Microsoft deliberately makes html email appear (and stay) in Outlook's top-posting, indented format. Since they cannot push RTF upon the world, they're trying to push the Outlook email format paradigm in order to build mind-share in their locked-in market and sue any 3rd party program that uses the Patented Proprietary Outlook Email Format.
>
>IMHPO (in my humble paranoid opinion)
></tinfoil_hat>
>
>
>
>*****
>
>The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA625
>
>
>
>
>
>
>
Received on 2008-02-21 20:58:24 CET