Re: svn co without -r gives confusing results

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."

There is no problem here. Check out the HEAD of the trunk (meaning:
check out the trunk without the -r argument), modify the working copy
as you see fit, and commit. If nobody else has committed yet, then
your commit to the trunk will be revision 147. If other commits have
been made to the repository in the meantime, then the revision number
will be larger. The revision of the repository only means "the number
of commits that have been made to the repository," nothing more.

Have you read the book? It explains the basics of Subversion:

http://svnbook.org/

If your background is with CVS, there is even an appendix which
guides former CVS users.

-- 
To reply to the mailing list, please use your mailer's Reply To All  
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org