[Monotone-devel] [PATCH] Re: on the semantics of 'mtn mv'

Ok, I've implemented a 'fix' for this behaviour. I believe that mtn rename is now more consistent with mv(1). The attached patch includes updates for the code, docs and tests. The diff is against revision b78672c7f625a5875db79b4a27567e751e1103bc The log message I used locally is: *

Re: [Monotone-devel] [PATCH] Re: on the semantics of 'mtn mv'

In message [EMAIL PROTECTED] on Mon, 30 Jul 2007 10:56:33 -0400, Ben Walton [EMAIL PROTECTED] said: bdwalton As an aside (and I haven't tested at all), were keys and bdwalton permissions that existed on venge.net moved over directly to bdwalton monotone.ca? Yes, as far as I can tell. I never

Re: [Monotone-devel] [PATCH] Re: on the semantics of 'mtn mv'

Ok, then I could likely commit this patch directly. Thanks -Ben On 7/30/07, Richard Levitte [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED] on Mon, 30 Jul 2007 10:56:33 -0400, Ben Walton [EMAIL PROTECTED] said: bdwalton As an aside (and I haven't tested at all), were keys and

[Monotone-devel] Re: [PATCH] Re: on the semantics of 'mtn mv'

I should have added earlier that the aforementioned patch corrects and/or makes consistent all 4 of the cases I initially presented. Thanks -Ben On 7/30/07, Ben Walton [EMAIL PROTECTED] wrote: Ok, I've implemented a 'fix' for this behaviour. I believe that mtn rename is now more consistent