Ben Collins-Sussman wrote:
>
> On Feb 1, 2005, at 10:32 PM, Steve Cohen wrote:
>
>>>
>> Okay, Travis and Ben, let me see if I understand this "Mixed Revision"
>> business after having read the relevant manual portion. This folder
>> was at revision 2. When I added C2.java to the repository, thereby
>> committing rev 16, this only applied to the new files, not to the
>> directory itself. Therefore, it was necessary to do an svn update,
>> which did bring the whole directory up to revision 16. Do I have that
>> right?
>>
>
>
> Correct. When you commit things, only the *committed* things get the
> newly committed revision. Ergo, if you just keep on running 'svn
> commit' forever, and never running 'svn up', your working copy
> essentially has every revision represented in it!
>
> To see that, run 'svn status -v'.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
okay, I see that. But I guess it's still a little hard to get my mind
around this concept, and probably svn help list should be revised
because it says nothing about it this strange feature. It should say
something to the effect of "when listing a directory the list is
relative to the current revision level of that directory". I guess I
don't see the point of the svn list command at all, because svn status
seems to be more informative and useful.
I can't quite get my mind around what makes the following a useful
feature (a further consequence of my previous example):
Assume I now check in revision 17 of C1.java but don't update (and also
abbreviate the "list" command to show the source of my discomfort):
$ svn ls -v
2 scohen 401 Jan 29 12:10 A.java
2 scohen 576 Jan 29 12:10 C1.java
$ svn ls C1.java -v
17 scohen 523 Feb 02 09:17 C1.java
with regular "ls" as we've all come to know and love it, if you list a
directory, and then list a single file within that directory the
listings for that file are identical. In svn ls, this is not
necessarily the case.
I understand what is going on; what I don't understand is why the
authors of svn want it this way.
Steve Cohen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 2 14:04:03 2005