[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Possible bugs in log -g

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: Mon, 18 Feb 2008 15:43:47 -0600

[I'll look at all the problems, but I wan to take them one at a time to
avoid possible dependencies.]

Mark Phippard wrote:
...
> 2) Too much mergeinfo. Incorrect filtering?
>
> svn log -g -r17 trunk
>
> This should really just show r16, but winds up showing a ton more.
> r15 gets pulled in and this was a big synch up merge from trunk. So
> this should get filtered out.

I get the following:
$ svn pg svn:mergeinfo trunk/
/branches/a:3-11
/branches/b:10-13
/branches/c:5-16
/trunk:2
$ svn pg svn:mergeinfo trunk/@16
/branches/a:3-11
/branches/b:10-13
/trunk:2

And the mergeinfo diff as detected by 'log -g' is '/branches/c:5-16',
which is correct, and that's the history that it is tracing. Maybe you
could help me understand why should we not pull in everything, all of
5-16. If we should stop somewhere, how do we tell when to stopping
tracing history?

-Hyrum

Received on 2008-02-18 22:44:01 CET

This is an archived mail posted to the Subversion Dev mailing list.