On Fri, Nov 19, 2010 at 12:25 PM, Stefan Sperling s...@elego.de wrote:
Hi All,
The short story, the following behaviors are intentional:
A) WC-to-WC [copies | moves]: Destination only gets explicit mergeinfo
if the source has it.
B) URL-to-[WC | URL] [copies | moves]: Destination gets explicit
On Wed, Nov 24, 2010 at 6:31 AM, Paul Burba ptbu...@gmail.com wrote:
On Fri, Nov 19, 2010 at 12:25 PM, Stefan Sperling s...@elego.de wrote:
Hi All,
The short story, the following behaviors are intentional:
A) WC-to-WC [copies | moves]: Destination only gets explicit mergeinfo
if the
On Fri, Nov 19, 2010 at 01:40:42PM +1000, Daniel Becroft wrote:
On Tue, Nov 16, 2010 at 3:54 PM, Daniel Becroft djcbecr...@gmail.comwrote:
Hi,
I've just found (another) issue with using URL-only renames. If one of the
parent directories has svn:mergeinfo recorded on it, then renaming a
On Fri, Nov 19, 2010 at 12:10 PM, Stefan Sperling s...@elego.de wrote:
On Fri, Nov 19, 2010 at 01:40:42PM +1000, Daniel Becroft wrote:
On Tue, Nov 16, 2010 at 3:54 PM, Daniel Becroft djcbecr...@gmail.comwrote:
Hi,
I've just found (another) issue with using URL-only renames. If one of the
On Tue, Nov 16, 2010 at 3:54 PM, Daniel Becroft djcbecr...@gmail.comwrote:
Hi,
I've just found (another) issue with using URL-only renames. If one of the
parent directories has svn:mergeinfo recorded on it, then renaming a file
via a URL results in the new file containing a full copy of what
Hi,
I've just found (another) issue with using URL-only renames. If one of the
parent directories has svn:mergeinfo recorded on it, then renaming a file
via a URL results in the new file containing a full copy of what was on the
trunk (but cut down to the individual file).
Please see the
