Travis P wrote:
>
> On Feb 1, 2005, at 9:41 PM, Steve Cohen wrote:
>
>> Why am I seeing this?
>
> ...
>
>> There are not 2 revisions, there are 16. 16 is the latest. Why are
>> both the list command and the info command stuck on the idea that
>> revision 2 is the latest, unless revision 16 is specified on the command
>> line? If I look at the repository through a web server
>> (http://localhost/svn/myproj/trunk/src/java/org/javactivity/game), I see
>> revision 16.
>
>
> Take a look at the info about mixed repositories in the Subversion book.
>
> I believe that:
>
> "svn list -v" has an implied argument of "." -- the directory in your
> working copy (WC), which is most likely at rev 2. The repos is not
> accessed over the network for this information.
>
> "svn list -r 16 -v" goes to the repository because you specified the
> revision you want and since your WC is at a different rev (rev 2), the
> repos must be asked what is in rev 16.
>
> If you were to do an "svn up; svn list -v", you'll get the answers you
> are expecting.
>
> -Travis
>
>
>
Yup, this works. But I don't understand why my directory was "at" rev
2, when in fact, all of the commits that raised the repository to rev 16
came from this very same directory. Is it necessary to do an update
after every commit? Could this be a bug in subeclipse, from which the
updates were done?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 2 05:21:13 2005