"Daniel Gehriger" <gehriger@linkcad.com> writes:
> Also, I found that 'svn diff' is very picky -- either I know the correct
> release numbers, or I have to start guessing. Even 'svnshell.py' does not
> seem to report the correct revision numbers. In the above /vendor directory,
> I used 'setrev 27' to switch to the youngest revision. Indeed, "test.txt"'s
> revisionis shown as 27. Then I do a 'setrev 26'. Now, "test.txt"'s revision
> is 24 ??? Why ? And when I request a diff -r 24:27, it doesn not work, but
> diff -r 26:27 does. How am I supposed to find the revision number 26, since
> it isn't displayed anywhere...?
What you are seeing is (essentially) the last revision in which the
node in our versioning filesystem changed. Keep in mind that
Subversion uses global revision numbers, so "revision 24 of test.txt"
doesn't mean that that file has been edited 24 times -- it simply
means "the snapshot of test.txt at the time global revision 24 was
created."
Judging by your example, it would seem that test.txt was modified in
revisions 24 and 27 (perhaps among others, too), but not in 25 or 26.
By "diff -r 24:27 ... doesn't work", what do you mean? You saw no
diffs? What output do you get when you run 'svn log -v test.txt'?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 14 20:02:48 2003