Yes, but, Subversion has 'one' latest version for the whole repository, in your case 146.
It just happens that no files in trunk have been updated since 131, but they all exist in 146, and 145, 144, 143 etc.
RTM again, it'll come, trust me.
Scott
-----Original Message-----
From: Jan Holec [mailto:jholec@retia.cz]
Sent: 13 April 2007 14:47
To: users@subversion.tigris.org
Subject: Re: svn co without -r gives confusing results
Dear Andreas,
first of all, let me thank you for taking the time to help.
I really do appreciate it.
I will try to be more specific in the following example:
after checking out working copies explicitly, by revision numbers
svn co file:///repository/projectname/trunk r131 -r131
svn co file:///repository/projectname/branches/3.02 r146 -r146
I get two directories, r131/ and r146/
and yes, those two checked-out trees do really differ:
$ ls -l r131/archiving/index.php r146/archiving/index.php
-rw-r--r-- 1 jholec users 18179 2007-04-13 13:42
r131/archiving/index.php
-rw-r--r-- 1 jholec users 18227 2007-04-13 13:42
r146/archiving/index.php
$ ls -l r131/monitoring/play.php r146/monitoring/play.php
-rw-r--r-- 1 jholec users 848 2007-04-13 13:41 r131/monitoring/play.php
-rw-r--r-- 1 jholec users 765 2007-04-13 13:42 r146/monitoring/play.php
$ ls -l r131/application.php r146/application.php
-rw-r--r-- 1 jholec users 5955 2007-04-13 13:42 r131/application.php
-rw-r--r-- 1 jholec users 5895 2007-04-13 13:42 r146/application.php
$ ls -l r131/lib/lang.conf.core.php r146/lib/lang.conf.core.php
-rw-r--r-- 1 jholec users 44738 2007-04-13 13:42
r131/lib/lang.conf.core.php
-rw-r--r-- 1 jholec users 45736 2007-04-13 13:42
r146/lib/lang.conf.core.php
(..there are more differences)
However, when I run just
svn co file:///repository/projectname/trunk th
A .....
.......
Checked out revision 146.
(a new directory 'th' is created)
$ cd th
$ svnversion
146
$ svn status -v
(all files are reported to be revision 146)
(still in th/)
$ ls -l application.php
-rw-r--r-- 1 jholec users 5955 2007-04-13 15:34 application.php
$ ls -l archiving/index.php
-rw-r--r-- 1 jholec users 18179 2007-04-13 15:34 archiving/index.php
$ ls -l lib/lang.conf.core.php
-rw-r--r-- 1 jholec users 44738 2007-04-13 15:34
lib/lang.conf.core.php
$ ls -l monitoring/play.php
-rw-r--r-- 1 jholec users 848 2007-04-13 15:34 monitoring/play.php
See? their sizes actually correspond to R131.
Regards,
Jan Holec <jholec at retia.cz>
Andreas Schweigstill píše v Pá 13. 04. 2007 v 14:30 +0200:
> Hello!
>
> Jan Holec schrieb:
> > That Subversion's revision numbers apply to entire trees and not
> > individual files,
>
> Not just entire trees but the whole repository...
>
> >> Nobody says that there has to be changed anything between
> >> R131 and R146.
> >>
> > ...because those revisions are definitely not the same.
> > Compared R146 to R131, some files have been modified,
> > some have been added.
>
> I never said that there shouldn't be a difference. Of course
> somewhere in the repository something must have changed, otherwise
> the revision number wouldn't have been increased.
>
> But this doesn't mean that on the sub-tree which has been checked
> out to a working copy there must be a change.
>
> > Just one example:
> > svn co file:///repository/xyz/trunk r131 -r131
> > svn co file:///repository/xyz/branches/3.02 r146 -r146
>
> So what?
>
> With best regards
> Andreas Schweigstill
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 13 15:45:34 2007