[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Weird behavior from checkout

From: Daniel Berlin <dberlin_at_dberlin.org>
Date: 2005-03-09 18:55:47 CET

If you use svn co -r 2 <path>, the server will open every single
revision, and eventually give you revision 2

if you use svn co -r 2 <path>@2, the server will open revisions 2, and
1, and give you revision 2.

This is because the peg_revision that gets passed down by checkout to
trace_node_locations will be <HEAD> in the first case, and 2, in the
second case.

In both cases, the start revision number will be correct.

I don't understand why the first shouldn't do the exact same thing as
the second on the server.

The attached patch gives me the desired behavior.

All it does is say "when you've specified a start revision, use that as
the peg revision".

After all, it doesn't seem to make sense to say something like:

svn co -r 5 <path>@41081

svn co -r 4 <path>@3

I could warn about conflicts between peg and start if we want.

So what i am missing?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Received on Wed Mar 9 18:57:30 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.