After successful rebase, write to the console how to undo the operation

[Kirill Müller]

bzr uncommit outputs a message like this:

You can restore the old tip by running:
  bzr pull . -r revid:<email address hidden>

Such a message would be even more important for the rebase command.

[Jelmer Vernooij (jelmer)]

I don't really see why it would be more important, but it would indeed be nice to do.

[Kirill Müller (krlmlr)]

For me, it would be to be able to undo the rebase (or later, histedit) in case something went wrong or the user decides otherwise.

[Kirill Müller (krlmlr)]

It is _more_ important because an uncommit can be undone easily by a following bzr qci (using the proposed log message) or by a plain commit and reentering the log message. Try to do this after a rebase.

[Jelmer Vernooij (jelmer)]

Running bzr commit in that situation won't give you the old commit back either, it will create a new commit.

[Kirill Müller (krlmlr)]

Thanks to tiplog, this is more or less a 'wishlist' now. On that note -- good to have the tiplog plugin, thanks for writing it!

[Jelmer Vernooij (jelmer)]

On 09/24/2011 10:43 PM, Kirill Müller wrote:
> Thanks to tiplog, this is more or less a 'wishlist' now. On that note --
> good to have the tiplog plugin, thanks for writing it!
>
tiplog certainly makes it a lot easier, but it was always possible to go
"bzr heads --dead --by-date", picking the first revision and then
running "bzr pull -rrevid:<that-revision> .".

Cheers,

Jelmer