Commit f69a8be
committed
sequencer: remember special error conditions
A cherry-pick can fail in surprising ways. For example, if it would
overwrite an untracked file, it does not even start to do anything, let
alone record that it is cherry-picking.
To discern such cases from regular error conditions where the user
simply has to resolve a merge conflict and then can call `git commit` to
finalize the cherry-pick (reusing the original commit message), such a
"really fatal" error is indicated by using an exit code != 1.
This means that we have to remember such an exit code by OR'ing later
error conditions.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>1 parent 2748862 commit f69a8be
1 file changed
Lines changed: 5 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
807 | 807 | | |
808 | 808 | | |
809 | 809 | | |
810 | | - | |
| 810 | + | |
811 | 811 | | |
812 | 812 | | |
813 | 813 | | |
| |||
945 | 945 | | |
946 | 946 | | |
947 | 947 | | |
948 | | - | |
| 948 | + | |
949 | 949 | | |
950 | 950 | | |
951 | 951 | | |
952 | 952 | | |
953 | 953 | | |
954 | 954 | | |
955 | | - | |
| 955 | + | |
956 | 956 | | |
957 | 957 | | |
958 | 958 | | |
| |||
987 | 987 | | |
988 | 988 | | |
989 | 989 | | |
990 | | - | |
| 990 | + | |
991 | 991 | | |
992 | 992 | | |
993 | 993 | | |
994 | | - | |
| 994 | + | |
995 | 995 | | |
996 | 996 | | |
997 | 997 | | |
| |||
0 commit comments