[Top][All Lists]

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

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

From: Samium Gromoff
Subject: Re: [Gnu-arch-users] Re: How to back out a change
Date: Tue, 09 Dec 2003 13:01:03 +0300
User-agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/21.3 (i386-pc-linux-gnu) MULE/5.0 (SAKAKI)

At Mon, 8 Dec 2003 08:11:46 -0800 (PST),
tom wrote:
>     > From: David Allouche <address@hidden>
>     > Mhh... just a question while we are at it.
>     > Is is "correct" (it the sense that the various merge tools will
>     > behave appropriately) to back-out a change which is not the
>     > latest revision (but, say, the one-to-last revision) with replay
>     > --exact --reverse?
> 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.

> 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?

> -t

regards, Samium Gromoff

reply via email to

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