Dain Sundstrom wrote:
[...]
> svn co -r 2473 https://svn.codehaus.org/openejb/trunk/openejb2
>
> Unfortunately, this doesn't work because an svn 1.3.1 client seems to
> follow the lineage directory which had moved. After a long chat on
> IRC, I got the correct command [2]:
>
> svn co https://svn.codehaus.org/openejb/trunk/openejb2@2473
>
> My confusion was confounded because a fiend of mine still has a 1.1.4
> client and the first command worked fine for him. I personally find
> the first format more natural, but can understand why the second was
> chosen...
Note that the two command syntaxes are both valid and both useful in certain
contexts, but they have different meanings. It is a nuisance that the meaning
of your first command has changed after version 1.1, but something had to
change because "-r" was not able to serve both purposes.
[...]
> I'm thinking of something like this
>
> $svn info
> Path: .
> URL: https://svn.codehaus.org/openejb/trunk/openejb2
> Permalink: https://svn.codehaus.org/openejb/trunk/openejb2@2473
[...]
That output would give the impression that the whole thing is a URL. In fact
it is not; URL + "@" + revision number is just a syntax that the "svn"
command-line client understands, and "-r URL" is another (with a different
meaning). I don't think this addition to "svn info" output is a good idea.
Instead, you might wish to consider adding something to the documentation in
the Subversion Book [1] or maybe in "svn help".
[1] See, for example, the section on "Peg Revisions",
<http://svnbook.red-bean.com/nightly/en/svn.advanced.pegrevs.html>.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jun 18 17:31:08 2006