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

Re: Weird behavior from checkout

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-03-09 19:05:55 CET

Daniel Berlin <dberlin@dberlin.org> wrote on 03/09/2005 12:55:47 PM:

> 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.
> svn co -r 5 <path>@41081
> or
> svn co -r 4 <path>@3
> I could warn about conflicts between peg and start if we want.
> So what i am missing?

Say you have a folder named "foo" that is moved to "bar" in r3. If you
then run the following commands:

svn co -r 2 url://bar

will succeed and checkout foo.

svn co -r 2 url://foo

will fail, because there is no foo at HEAD.

That is what the peg revisions are for. The default of HEAD means that
you want revision 2 of what is currently named "bar".


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 9 19:07:12 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.