You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Hojin Choi <py...@users.kldp.net> on 2004/10/15 07:36:46 UTC
Re: Copy/Move issues
Sorry for reminding old mail.
I have encounterred same problem like below mail.
Isn't it supported yet to copy/move between repository at svn 1.1.0?
----- Original Message -----
From: "Ben Collins-Sussman" <su...@collab.net>
To: <al...@ps.ge.com>
Cc: "svn-dev-list" <de...@subversion.tigris.org>; <us...@subversion.tigris.org>
Sent: Tuesday, July 13, 2004 11:02 PM
Subject: Re: Copy/Move issues
> On Tue, 2004-07-13 at 04:31, alwin.vandriel@ps.ge.com wrote:
>>
>> 2. We also want to move sources from one repository to another repository
>> using the move command. When performing this action the target repository
>> gets corrupted and can only be repaired by the Recover command. First this
>> seems like a bug but secondly is this move action supported anyway?
>
> No, you cannot copy or move data between repositories. And if you want
> specific answers, you'l have to show us what you mean by "the target
> repository gets corrupted". If you try to run 'svn mv/cp URL1 URL2' and
> the two URLs represent different repositories, you should get a simple
> error. There's nothing that should cause BerkeleyDB to wedge. Show us
> details.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Copy/Move issues
Posted by geoff <ot...@0x29a.org.uk>.
On Fri, 15 Oct 2004 16:36:46 +0900, "Hojin Choi"
<py...@users.kldp.net> wrote:
>Sorry for reminding old mail.
>I have encounterred same problem like below mail.
>
>Isn't it supported yet to copy/move between repository at svn 1.1.0?
Not a copy/move with history.
You can do an OS copy and lose the history. Do an SVN delete in the
source wc and an add in the dest wc, commit both wcs, and you've just
done a move.
I heard a rumour on the Tortoise list that the configuration
TortoiseSVN 1.1.1
SVN 1.1.1
Apache 2.0.52
at least doesn't wedge your repository when you try to do this and
fail.
Anybody know which change fixed this? Which issue described it?
I toured CHANGES on the trunk and found nothing to match.
--
best,
geoff
regrettably the email address above will bounce
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org