Moving is equivalent to copy/delete according to the manual so I tried
copying and the copy works OK but the log stays where it is and a new
one with the comment, in my case, "Copied remotely" is created. So it
looks like a move would lose my log. Thanks for your reply though.
It is beginning to seem that the only way to achieve what I want is by a
backdoor dump/manually edit/restore approach as someone else has
suggested.
I think the problem is that Subversion faithfully tries to reflect all
modifications, as it is meant to do. What I want is to say, "No no, I
screwed up, forget about all that!"
John B.
-----Original Message-----
From: Anders J. Munch [mailto:ajm@flonidan.dk]
Sent: Friday, 19 May 2006 7:04 PM
To: John Bonnett, R&D Australia
Cc: users@subversion.tigris.org
Subject: Re: Creating trunk later
From: Ryan Schmidt [mailto:subversion-2006q2@ryandesign.com]
> On May 19, 2006, at 06:38, jbonnett wrote:
>
> > I have a history of revisions built up in https://repository/prog1
> > and would like to move everything to https://repository/prog1/
> > trunkincluding my revision history. I don't seem to be able to do
> > this. The revision history seems to want to stay in the old
> location.
>
> What does that mean? How are you moving it? Isn't it just
>
> svn mv https://repository/prog1 https://repository/prog1/trunk
No, you can't move something to within itself.
A temporary renaming should do it:
# WARNING UNTESTED
svn move https://repository/prog1 https://repository/othername
svn mkdir https://repository/prog1
svn move https://repository/othername https://repository/prog1/trunk
- Anders
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 22 01:56:03 2006