Ben Collins-Sussman wrote:
>
> On Oct 20, 2004, at 9:01 AM, Andrew Arnott wrote:
>
>> I just asked this question a few days ago. See the thread with
>> subject "Reverse last commit". But here was the most useful answer I
>> received:
>>
>> This should be executed on the server. No, there is not simpler way
>> (that I know of):
>>
>
> Sure there's a simpler way. If you commit the reverse-merge of
> revision N, then revision N+1 (the new HEAD) is identical to revision
> N-1. This is what chapter 4 describes. Much simpler than dumping and
> reloading the whole repository!
To clarify: what Arnold wanted to do was remove all traces of the commit
from the repository, thus the dump/load cycle. If this doesn't concern
you, you can simply take the "reverse merge" approach. Merges can't be
done server-side, so you'd need to do this in your working copy (i.e.
apply the reverse merge to your WC and then commit those changes).
A simple "svn merge -r COMMITTED:PREV ." followed by a commit should do
the trick, but read the section in chapter 4 and examine the diffs
before you commit them to make sure you're getting what you want. When
you commit, use a meaningful message like "reversing changes from r123".
toby
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 20 17:48:23 2004