On Tue, 06 Jul 2004 02:14:54 +0200, Branko Čibej <brane@xbc.nu> wrote:
>
>
> Garrett Rooney wrote:
>
> >On 05 Jul 2004 12:04:17 -0500, kfogel@collab.net <kfogel@collab.net> wrote:
> >
> >
> >>So, here's a wicked question: shouldn't an offset of "HEAD-10" on a
> >>file show you the last ten revisions *in which that file changed*, not
> >>simply the revisions numbered HEAD through HEAD-10? :-) (Or did your
> >>code already do that, and I just missed it?)
> >>
> >>
> >It does do that already ;-) The repos level functions use the path
> >you gave it to root the history, then go back in time using that, so
> >you start at the most recent rev in which that item changed and move
> >back through the list of revs where it changed. It pretty much works
> >the way I'd expect it to, and if I'm reading your question right I
> >think it works the way you'd expect it to ;-)
> >
> >
> So. Implement this, go a trunk working copy, and do:
>
> svn log -rHEAD:HEAD-3 COMMITTERS HACKING
>
> In your interpretation, HEAD-3 is currently r9966 for COMMITTERS, but
> r9793 for HACKING. I think both of you are expecting a can opener -- for
> cans of worms. :-)
That's why the patch I sent only allows a single target for the
bounded version of log ;-)
If we allow more than one target I believe the correct behavior would
be to get the last N revs for each target, merge them all together and
then return the most recent N from the merged set. I'm not sure if
this is usefull enough to bother implementing it though.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 6 02:19:54 2004