On Sun, Dec 02 2018, Jeff King wrote: > On Sat, Dec 01, 2018 at 09:28:47PM -0500, Eric Sunshine wrote: > >> On Sat, Dec 1, 2018 at 3:02 PM Jeff King <peff@xxxxxxxx> wrote: >> > On Thu, Nov 29, 2018 at 09:32:48AM +0100, Johannes Schindelin wrote: >> > > In reality, I think that it would even make sense to change the default to >> > > reschedule failed `exec` commands. Which is why I suggested to also add a >> > > config option. >> > >> > I sometimes add "x false" to the top of the todo list to stop and create >> > new commits before the first one. That would be awkward if I could never >> > get past that line. However, I think elsewhere a "pause" line has been >> > discussed, which would serve the same purpose. >> >> Are you thinking of the "break" command (not "pause") which Dscho >> already added[1]? >> >> [1]: 71f82465b1 (rebase -i: introduce the 'break' command, 2018-10-12) > > Yes, thanks (as you can see, I haven't actually used it yet ;) ). Related: I got poked about a bug where someone was doing "exec bash" to do the same, and would then CD to other repos, and git operations would still be executed on the original repo because we set GIT_DIR=* in the envioronment (but not for "break"). Not a big deal, but I wondered if that was a bug in itself, i.e. if we need to set GIT_DIR et al in the environment for "exec". Isn't having the current directory set to the checkout sufficient?
