--- Noel Yap <yap_noel@yahoo.com> wrote:
> > 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.
>
> Thanks for clearing this up. It's all crystal clear
> now. The more I learn about Subversion, the more I
> like it :-)
Like I said in my last post, I like this feature of
Subversion.
OTOH, unless I'm mistaken, a PREV(rev) functionality
would still be helpful in implementing "svn blame" (or
"svn etiology" ;-). I'm thinking the command can be
implemented by going backwards through the physical
revision history (eg the revisions in which the file
really changed) of the file and annotating the file
along the way. PREV(rev) would go a long way in
helping with this unless there's a better way to
implement it.
OTOOH, maybe PREV isn't the way to go since "svn
blame" is used on a per-file basis rather than on an
entire tree. Anyway, the functionality would still be
helpful (unless I'm still missing something) even if
it's not called PREV.
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:39:02 2002