[PATCH 0/1] Make rebase.reschedulefailedexec less overzealous

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This config setting is pretty useful, but it unfortunately stops all
non-interactive rebases with a bogus error message. This patch fixes that.

Reported via a commit comment on GitHub
[https://github.com/git/git/commit/969de3ff0e0#commitcomment-33257187].

Johannes Schindelin (1):
  Let rebase.reschedulefailedexec only affect interactive rebases

 builtin/rebase.c           | 7 +++++--
 t/t3418-rebase-continue.sh | 8 ++++++++
 2 files changed, 13 insertions(+), 2 deletions(-)


base-commit: e11ff8975bedc0aae82632c3cb72578c3d7fc0b2
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-253%2Fdscho%2Freschedule-failed-exec-gently-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-253/dscho/reschedule-failed-exec-gently-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/253
-- 
gitgitgadget



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux