| commit | 214123c6457d9706716dbdd608d03262e348a121 | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Tue, 8 Mar 2016 23:51:36 +0000 (8 15:51 -0800) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 10 Mar 2016 23:35:48 +0000 (10 15:35 -0800) | ||
| tree | a3c67598abcf7d79966127e4b7ed663f1049f7d4 | treesnapshot (tar.gz zip) |
| parent | 71b401032b9e5b0a71e41d95ae0998858787700c | commitdiff |
rebase-i: clarify "is this commit relevant?" test
While I was checking all the call sites of sane_grep and sane_egrep,
I noticed this one is somewhat strangely written. The lines in the
file sane_grep works on all begin with 40-hex object name, so there
is no real risk of confusing "test $(...) = ''" by finding something
that begins with a dash, but using the status from sane_grep makes
it a lot clearer what is going on.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
While I was checking all the call sites of sane_grep and sane_egrep,
I noticed this one is somewhat strangely written. The lines in the
file sane_grep works on all begin with 40-hex object name, so there
is no real risk of confusing "test $(...) = ''" by finding something
that begins with a dash, but using the status from sane_grep makes
it a lot clearer what is going on.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| git-rebase--interactive.sh | diffblobblamehistory |