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

Re: svn log -g problems

From: Mark Phippard <markphip_at_gmail.com>
Date: Tue, 4 Mar 2008 21:33:50 -0500

On Tue, Mar 4, 2008 at 8:40 PM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
> Mark Phippard wrote:
> > svn log -g -r29649:29689 http://svn.collab.net/repos/svn.1.5/branches/1.5.x
> >
> > This gives no output at all. Removing the -g works fine. Reversing
> > the revision numbers and leaving the -g also works, except there is no
> > "-g" output included.
>
> No, reversing the revision numbers does include -g output. See r29671 in
> the output below?
>
> $ svn log -r29689:29649 http://svn.collab.net/repos/svn.1.5/branches/1.5.x -gq
> ------------------------------------------------------------------------
> r29689 | hwright | 2008-03-03 21:15:10 -0500 (Mon, 03 Mar 2008)
> ------------------------------------------------------------------------
> r29671 | cmpilato | 2008-03-03 11:35:14 -0500 (Mon, 03 Mar 2008)
> Merged via: r29689

I thought this might be the case, but did not go back and look.
Basically it is the same problem as the other where it only shows
once.

> I notice that there appear to be three merges in the specified range, but
> only one of them is a merge of revisions also in the specified range. Is
> this reflected in the output above? Meaning, are we only seeing the one -g
> revision (r29671) because the other merges are of revisions earlier than r29649?

I thought of that too, and it is possible that is related. However, I
have been seeing this problem of only showing once when doing a 0:HEAD
log as well as the --stop-on-copy.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-05 03:34:01 CET

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