| commit | 6ea3b67b4e3f4a09561a26ca42af1492b3b48c95 | |
| author | Paul Tan <pyokagan@gmail.com> | |
| Sat, 6 Jun 2015 11:46:12 +0000 (6 19:46 +0800) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 8 Jun 2015 20:14:04 +0000 (8 13:14 -0700) | ||
| tree | 6f7bfe24a83d37a90c3efc9d05e29579cd93d58d | treesnapshot (tar.gz zip) |
| parent | e06764c8ebf87a80737dc0a6198a013799f18e32 | commitdiff |
am --abort: keep unrelated commits on unborn branch
Since 7b3b7e3 (am --abort: keep unrelated commits since the last failure
and warn, 2010-12-21), git-am would refuse to rewind HEAD if commits
were made since the last git-am failure. This check was implemented in
safe_to_abort(), which checked to see if HEAD's hash matched the
abort-safety file.
However, this check was skipped if the abort-safety file was empty,
which can happen if git-am failed while on an unborn branch. As such, if
any commits were made since then, they would be discarded. Fix this by
carrying on the abort safety check even if the abort-safety file is
empty.
Signed-off-by: Paul Tan <pyokagan@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Since 7b3b7e3 (am --abort: keep unrelated commits since the last failure
and warn, 2010-12-21), git-am would refuse to rewind HEAD if commits
were made since the last git-am failure. This check was implemented in
safe_to_abort(), which checked to see if HEAD's hash matched the
abort-safety file.
However, this check was skipped if the abort-safety file was empty,
which can happen if git-am failed while on an unborn branch. As such, if
any commits were made since then, they would be discarded. Fix this by
carrying on the abort safety check even if the abort-safety file is
empty.
Signed-off-by: Paul Tan <pyokagan@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| git-am.sh | diffblobblamehistory | |
| t/t4151-am-abort.sh | diffblobblamehistory |