Re: log -g problem when performed on files

On Thu, May 8, 2008 at 9:43 AM, Marc Strapetz <marc.strapetz_at_syntevo.com> wrote:
> > That is definitely the way it is expected to work. There is no
> > possibility of changing this. Subversion does not really know if a
> > commit is the result of a merge,
>
> That's understandable.
>
> > all it can really do is report on changes to the mergeinfo property.
>
> So for my example Subversion doesn't knows at r10 but just at r11 that
> changes have been merged so it could report the corresponding revisions from
> the branch at r11? (What it currently does not do.)

As I recall from your example, you did svn log -g on the file. The
file was not changed in r11. Only a parent folder was changed. If
you ran svn log -g on that folder presumably it shows some merge
output?

-- 
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