Re: Generating a todo file for non-interactive rebasing

2019-04-17 Thread Drew DeVault
Thanks for clarifying this, folks. On 2019-04-17 6:11 PM, Johannes Schindelin wrote: > To my surprise, Elijah Newren (who authored that change) then demonstrated > that in most cases, the `--merge` backend is actually *faster* than the > default (`--am`) backend. There were patches floating aroun

Re: Generating a todo file for non-interactive rebasing

2019-04-17 Thread Johannes Schindelin
Hi Drew, On Tue, 16 Apr 2019, Drew DeVault wrote: > 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 planne

Re: Generating a todo file for non-interactive rebasing

2019-04-17 Thread Phillip Wood
Hi Drew On 16/04/2019 16:37, Drew DeVault wrote: 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

Generating a todo file for non-interactive rebasing

2019-04-16 Thread Drew DeVault
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'