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

Re: svn co without -r gives confusing results

From: Jan Holec <jholec_at_retia.cz>
Date: 2007-04-13 12:57:36 CEST

Ryan Schmidt píše v Pá 13. 04. 2007 v 04:33 -0500:
> On Apr 13, 2007, at 04:22, Jan Holec wrote:
>
> > I don't quite understand the way 'svn checkout' works.
> >
> > Example:
> > I want to check out the last revision on the trunk
> > (which is 131), so I run:
> >
> > svn co file:///repository/myproject/trunk myproject
> > A ....
> > ......
> > Checked out revision 146.
> >
> >
> > But - revision 146 is NOT located on the trunk at all!
> > It's on myproject/branches/3.02 (and it also happens to be
> > the last revision commited to the repository).
> >
> > -and-
> >
> > the checked-out sources really seem to be revision 131, not 146.
>
> Revision 146 is not located "on" the trunk or "on" any other path in
> the repository. Revisions in Subversion are of the repository as a
> whole, not of files or paths within it as with CVS.
>
> The following statements express your situation in the correct
> terminology:
>
> "The HEAD revision of the repository is 146."
> "The last changed revision of the trunk is 131."
Ok.

>
> There is no problem here. Check out the HEAD of the trunk (meaning:
> check out the trunk without the -r argument),
That's exactly what I intended to do, see above.
I expected svn to check out revision 131 - and from what I can tell
after inspecting the sources, it does - but then WHY is it telling me
it has checked out revision 146 ?!

> modify the working copy

Jan Holec <jholec at retia.cz>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 13 12:45:12 2007

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