Re: [Gnu-arch-users] Re: How to back out a change

[David Allouche]

On Tue, Dec 09, 2003 at 01:01:03PM +0300, Samium Gromoff wrote:
> At Mon, 8 Dec 2003 08:11:46 -0800 (PST),
> > 
> > That will remove the log files for the old revision which is sometimes
> > what you want and other times not.
> > 
> > Do you want the old (removed) revision to appear in `whats-missing'?
> > Do you want an (ordinary use of) `replay' to try to put it back?
> > That will be the effect of `replay --exact --reverse'.
> > 
> > On the other hand, if you want to leave the logs, you have to take two
> > steps (and, yes, these will be combined in a single convenience
> > command at some point but):
> > 
> >     tla replay --exact --reverse <patch-to-remove>
> >         tla sync-tree `tla tree-version`
> 
> And would the delta reversion itself will get a patch-log?
> 
> i.e. i back out a change, while leaving it in the archive, and
> add a specific comment which show what the revert has been done
> and why it was done.

Yes it will, because you will end up doing a commit after the "replay"
and the "sync-tree".

> > Well, let's suppose that you want to undo the very latest revision,
> > patch-N.   You could:
> >
> >     tla get proj--branch--1.0--patch-<N-1> dir
> >       cd dir
> >       tla sync-tree proj--branch--1.0--patch-N
> 
> OTOH, if i want the change to disappear from the archive, as if it
> was never committed, what do i do?

As usual: you remove the directory from the archive, taking care to move
the ++revision-lock to the new last revision.

But of course, you are putting yourself out the system (out of the
society anyone? :-P) when doing this. One basic rule in Arch is that you
cannot go backwards in time and you cannot change history. Any commited
change will stay in the history. And if the change is idiotic, then
there will be an eternal testimony of your idiocy in the archive.

-- 
                                                            -- ddaa