Hi Andrew,
I hope it's an existing capability, because I've used it.
At least I think I have. Something like:
>svn delete http://server/repos/proj/branches/a -m "delete the head"
Committed revision 101.
>svn copy -r99 http://server/repos/proj/branches/a
http://server/repor/proj/branches -m "copy r99 to head"
Committed revision 102.
Maybe not verbatim, but pretty much like that.
Walden
----- Original Message -----
From: "Andrew Arnott" <andrewarnott@gmail.com>
To: "Walden Mathews" <walden@eqwality.com>
Cc: <users@subversion.tigris.org>
Sent: Thursday, October 21, 2004 6:39 PM
Subject: Re: WG: Subversion pop quiz
| Are you suggesting a new capability? Or suggesting an existing one?
| I didn't know one could "delete the head".
|
|
| On Wed, 20 Oct 2004 13:22:52 -0400, Walden Mathews <walden@eqwality.com>
wrote:
| > For a totally server-side solution, how about deleting the HEAD,
| > then doing an svn copy from rev N-1? Of course, this assumes you
| > have eliminated the chance of other intervening commits, but if
| > you're the admin that's easy.
| >
| > Walden
| >
| > ----- Original Message -----
| > From: "Toby Johnson" <toby@etjohnson.us>
| > To: <users@subversion.tigris.org>
| > Sent: Wednesday, October 20, 2004 11:47 AM
| > Subject: Re: WG: Subversion pop quiz
| >
| >
| >
| >
| > | 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
| > |
| > |
| > | __________ NOD32 1.898 (20041020) Information __________
| > |
| > | This message was checked by NOD32 antivirus system.
| > | http://www.nod32.com
| > |
| > |
| >
| >
| >
| > ---------------------------------------------------------------------
| > To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
| > For additional commands, e-mail: users-help@subversion.tigris.org
| >
| >
|
|
| --
| Andrew Arnott
| Web Developer
| Brigham Young University
|
| ---------------------------------------------------------------------
| To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
| For additional commands, e-mail: users-help@subversion.tigris.org
|
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 22 00:54:39 2004