Thank you very much for clearing that up for me. You are right, I do
mainly use TortoiseSVN. That "stop on copy" option is just what I
needed. I had never noticed that check box down the bottom! (or knew
what it meant)
John B.
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2006q2@ryandesign.com]
Sent: Monday, 22 May 2006 8:21 PM
To: John Bonnett, R&D Australia
Cc: ajm@flonidan.dk; users@subversion.tigris.org
Subject: Re: Creating trunk later
On May 22, 2006, at 01:54, jbonnett wrote:
> 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!"
Your history is NOT lost. The fact that the message says "Copied
remotely" means you're probably using TortoiseSVN. Please note that
TortoiseSVN automatically uses the option "stop on copy" when showing
you a log. If you will turn off that option, or display a log from
the command line (where that option is not the default), the log will
not stop at places where you copy.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 23 01:16:34 2006