summaryrefslogtreecommitdiff
path: root/environment.c
diff options
context:
space:
mode:
authorJohannes Schindelin <johannes.schindelin@gmx.de>2017-01-02 16:28:34 +0100
committerJunio C Hamano <gitster@pobox.com>2017-01-09 14:57:30 -0800
commit9d7bf3cf993ab59e0f9d7150534213f57dd12741 (patch)
tree5894bfc7cbecbfcbf478bcb285ebcb19867bbbed /environment.c
parentca6c6b45dd9c36ae3e0b4f1fc9812d1e6a8b59bc (diff)
downloadgit-9d7bf3cf993ab59e0f9d7150534213f57dd12741.tar.gz
sequencer (rebase -i): allow rescheduling commands
The interactive rebase has the very special magic that a cherry-pick that exits with a status different from 0 and 1 signifies a failure to even record that a cherry-pick was started. This can happen e.g. when a fast-forward fails because it would overwrite untracked files. In that case, we must reschedule the command that we thought we already had at least started successfully. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'environment.c')
0 files changed, 0 insertions, 0 deletions