On Nov 20, 2006, at 19:28, John Rouillard wrote:
[Hypothetical syntax for creating a label:]
> With labels I:
>
> svn label -r 195 PRODUCTION http://repo/config/trunk/ldap/
> ldap.conf.solaris
> svn label -r 196 PRODUCTION http://repo/config/trunk/ldap/
> ldap.conf.linux
> svn label -r 199 PRODUCTION http://repo/config/trunk/ldap/
> ldap.conf.aix
>
> (note no working copy needed). Or maybe:
>
> svn label PRODUCTION http://repo/config/trunk/ldap/
> ldap.conf.solaris@195 \
> http://repo/config/trunk/ldap/ldap.conf.linux@196 \
> http://repo/config/trunk/ldap/ldap.conf.aix@199
If I understand your example, and you are suggesting potential
syntaxes for creating a label, and you are intending these to be
equivalent, then I must recommend the former, not the latter, because
the latter is not what the peg revision syntax "URL@PEGREV" currently
means. "URL@PEGREV" currently means "Find the object URL in
repository revision PEGREV and get its HEAD revision" which I don't
think is what you intended.
The operative revision syntax "-r OPREV URL", on the other hand,
which I believe is what you do want, means "Find the object URL in
the repository's HEAD revision, and get its revision OPREV."
More generally, combining the two, there is "-r OPREV URL@PEGREV"
which means "Find the object URL in repository revision PEGREV and
get its revision OPREV." Omitting either of these revisions defaults
it to HEAD.
FYI, peg revision documentation:
http://svnbook.red-bean.com/nightly/en/svn.advanced.pegrevs.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 21 08:30:41 2006