git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
* Generating a todo file for non-interactive rebasing
@ 2019-04-16 15:37 Drew DeVault
  2019-04-17 14:59 ` Phillip Wood
  2019-04-17 16:11 ` Johannes Schindelin
  0 siblings, 2 replies; 4+ messages in thread
From: Drew DeVault @ 2019-04-16 15:37 UTC (permalink / raw)
  To: git

Hiya!

Whenever I do a particularly long rebase on a branch, sorting out
conflicts from upstream, I find that it's often useful to have the
additional context that you get during an interactive rebase, such as
recent commands run, commands planned to run, and so on, to get a better
idea of where I'm at during the rebase. These show when you run `git
status` during an interactive rebase.

However, the code that generates this report relies on a todo list being
generated in the rebase state directory. A todo list which consists only
of "pick" commands is functionally equivalent to a non-interactive
rebase, the only difference being that the editor isn't shown to the
user.

Is there any reason not to refactor the rebase command to always
generate a todo list? This would simplify the internals and provide more
context to the user during hairy rebases. It might also be useful to run
--edit-todo if you realize your rebase strategy needs to change partway
through a rebase which was initially non-interactive.

Note: I'm a non-subscriber, please Cc me on replies.

-- 
Drew DeVault

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2019-04-17 17:11 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-04-16 15:37 Generating a todo file for non-interactive rebasing Drew DeVault
2019-04-17 14:59 ` Phillip Wood
2019-04-17 16:11 ` Johannes Schindelin
2019-04-17 17:11   ` Drew DeVault

Code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).