[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Removing the last changeset(s) from the archive

From: Charles Duffy
Subject: Re: [Gnu-arch-users] Removing the last changeset(s) from the archive
Date: Sun, 14 Nov 2004 13:13:42 -0600

On Sun, 2004-11-14 at 13:19 -0600, Karl O. Pinc wrote:
> On 2004.11.14 12:57 Aaron Bentley wrote:
> > Karl O. Pinc wrote:
> >> I'll fix the bug and commit the change, but do something
> >> wrong and accidently include portions of my larger problem
> >> in the commit.  It'd be nice to be able to 'do over'.
> > 
> > How about tla replay --reverse $REVSIION; tla sync-tree $REVISION; 
> > tla commit -s "undid botched bugfix"?
> So far, my solution is:
> tla commit -s 'Uh, commited more files that I should have. This revision
> and the last one are broken.'

You mean this?
$ tla commit -s 'Reverse botched commit; next one has standalone bugfix'.
I don't think that a reversal is necessarily broken by definition. In
any event, you should be able to tag around it, so that folks checking
out the latest version of your archive never pull the broken revisions,
even though they're never deleted. (This functionality is unbroken,

That, or you can go follow the instructions on the wiki to manually
tweak your archive (and do it very carefully). Unless, say, you're
mirrored at somewhere, or someone else has or mamy have cheecked out or
branched from your new revision, in which case that would be bad (in the
Ghostbusters sense).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]