--- Nuutti Kotivuori <naked@iki.fi> wrote:
> I think you have a bit of a misunderstanding here -
> or I do :) This is
> the same thing I mentioned earlier to you.
Judging from a similar post, I'm the one with the
misunderstanding.
> If a change happened at revision 53, on a branch -
> like it did here -
> then the change is returned by a diff of revision 52
> and 53. You do
> not have to go back and search the previous revision
> the same file (or
> directory) actually changed last.
>
> An example ought to clear this up.
>
> Assume a directory structure of
>
> /trunk/a
> /trunk/b
> /trunk/c
> /branches/dev/a
> /branches/dev/b
> /branches/dev/c
>
> Now commits
>
> revision 10: modified /trunk/b
> revision 11: modified /branches/dev/a
> revision 12: modified /trunk/a
> revision 13: modified /trunk/c
> revision 14: modified /branches/dev/a
>
> Now if we want to get the changeset for revision 14
> - all we have to
> do is 'svn diff -r13:14' on the correct path at the
> repository. We do
> not have to say 'svn diff -r11:14', though that
> would create the exact
> same result. So there is no need for PREV here at
> all.
>
> What is a problem though is finding the times when a
> certain file
> changed - or finding the last change to a file
> without a working
> copy. But those are separate problems, not a problem
> at the thing
> sussman is describing.
Thanks for clearing this up. It's all crystal clear
now. The more I learn about Subversion, the more I
like it :-)
Thanks,
Noel
__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 10 01:17:13 2002