Re: Bug? 'svn log' doesn't follow file-moves

Zack Brown <zbrown@tumblerings.org> writes:

> > `svn log` (without --strict) does follow file moves. However:
> >
> > rev 347: kfogel | 2001-10-29 16:20:47 -0600 (Mon, 29 Oct 2001) | 5 lines
> > Changed paths:
> > D /trunk/AUTHORS
> > A /trunk/COMMITTERS
> >
> > the absence of "(copied from ...)" on the COMMITTERS line above means
> > that the filesystem didn't log this operation as a true copy -- just
> > as an add and a delete.
>
> Is that possibly because the tree was patched by one of Subversion's unified
> diffs instead of a direct commit?

Possibly. Though, in this case, I think it was because we hadn't yet
implemented the 'move' command. :-)

> i.e. is there any way for someone without direct commit access to a
> tree, to submit a patch to properly rename a file?

Without a more robust patch format, no, this is not possible.

Our 'svn diff' output gets us per-file change support (like GNU diff
itself does). And while 'svn diff' also dumps out property mods in a
clumsy way, a) 'patch' sees that output as rubbish, and b) there is no
'svn patch' yet which would interpret that data as more than rubbish.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 3 23:03:18 2002