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

Re: Specifying Branch/Tag and Revision

From: Stefan Sperling <stsp_at_elego.de>
Date: 2007-11-20 20:05:02 CET

On Tue, Nov 20, 2007 at 10:47:03AM -0800, Rush Manbert wrote:
> I have svn copied trunk to branches/myTestBranch, which created revision
> 706 in my repository. I then tried this checkout:
> svn co svn+ssh://repos/base/branches/myTestBranch ~/myTestCheckout
> --revision 700
> The checkout completes and I do this:
> svn info ~/myTestCheckout
> and I see that the URL for the working copy is
> svn+ssh://repos/base/trunk
> I can understand why specifying revision 700 could trace back through the
> branch copy to the trunk. I assume the behavior would be the same for my
> tags directory tree.
> My question is this: Is this the expected behavior? My expectation was that
> this would fail because the branch doesn't exist in revisions prior to 706,
> so I was surprised by what I saw.

Subversion starts looking for myTestBranch at the currently highest
revision, traverses history back to rev 700 and along the way finds
out that your branch came from trunk.

Then it transparently checks out trunk at rev 700.

svn help co says:

  usage: checkout URL[@REV]... [PATH]
    If specified, REV determines in which revision the URL is first
    looked up.

So try this instead:

svn co svn+ssh://repos/base/branches/myTestBranch_at_700 ~/myTestCheckout

This should yield an error as you expected.

Stefan Sperling <stsp@elego.de>                 Software Developer
elego Software Solutions GmbH                            HRB 77719
Gustav-Meyer-Allee 25, Gebaeude 12        Tel:  +49 30 23 45 86 96 
13355 Berlin                              Fax:  +49 30 23 45 86 95
http://www.elego.de                 Geschaeftsfuehrer: Olaf Wagner

  • application/pgp-signature attachment: stored
Received on Tue Nov 20 20:08:29 2007

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

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