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

Re: svn cross-repo copy loses svn:executable *and* leaves the working dir inconsistent

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Mon, 29 Aug 2011 09:36:24 -0400

http://subversion.tigris.org/issues/show_bug.cgi?id=3590 documents some of
the history of this action (copy from a foreign repository). I have no idea
how 1.7 behaves in this same scenario, though I don't recall anyone
intentionally targeting this functionality.

That said, as it was me that filed that above issue, I'm clearly in favor of
allowing this sort of operation -- especially if it can preserve all the
node properties as part of the copy, too. I see this as very beneficial to
bootstrapping a foreign-repository-based vendor branch situation.

As for the text of the 1.6 book, I'm mostly responsible for that, too, and I
can tell you that I didn't re-test Subversion's behavior in this regard when
working on that version of the text. If the book is inaccurate, please send
a patch (or at least a notice of the problem) to svnbook-dev_at_red-bean.com.

On 08/29/2011 03:42 AM, Mark Eichin wrote:
> The 1.6 book has the same Note text, as does
> http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.copy.html - so at
> least it hasn't been documented any differently in that time. (So it
> at least appears that cross-repo cherry-picking isn't an
> intentionally-supported use case...)
>
> On Mon, Aug 22, 2011 at 2:25 PM, Hyrum K Wright
> <hyrum.wright_at_wandisco.com> wrote:
>> That text is from the 1.5 section of the book. 1.5 is over 4 years
>> old, so current behavior might be different...
>>
>> On Sun, Aug 21, 2011 at 8:48 PM, Mark Eichin <eichin_at_gmail.com> wrote:
>>> Huh. http://svnbook.red-bean.com/en/1.5/svn.ref.svn.c.copy.html
>>> actually has a Note:
>>> "You can only copy files within a single repository. Subversion does
>>> not support cross-repository copying."
>>>
>>> I guess that means that the bug is that it doesn't check uuids and
>>> actually *enforce* this; I'm sure I'm not the only one who'd be
>>> surprised to learn of this constraint - especially since merge doesn't
>>> have such a warning (and in fact cross-repo cherry-picking with svn
>>> merge is actually kind of important...)
>>>
>>>
>>>
>>> --
>>> _Mark_ <eichin_at_thok.org> <eichin_at_gmail.com>
>>>
>>
>>
>>
>> --
>>
>> uberSVN: Apache Subversion Made Easy
>> http://www.uberSVN.com/
>>
>
>
>

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2011-08-29 15:36:59 CEST

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