diff options
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | 2021-01-27 16:37:22 (GMT) |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2021-01-28 06:01:49 (GMT) |
| commit | 679b5916cdafdcfa9fb36c31dbf53d7e4aa0af0b (patch) | |
| tree | d3ad427618e272cc05cc4c8924f0ff3114612d04 /range-diff.c | |
| parent | 66e871b6647ffea61a77a0f82c7ef3415f1ee79c (diff) | |
| download | git-679b5916cdafdcfa9fb36c31dbf53d7e4aa0af0b.zip git-679b5916cdafdcfa9fb36c31dbf53d7e4aa0af0b.tar.gz git-679b5916cdafdcfa9fb36c31dbf53d7e4aa0af0b.tar.bz2 | |
range-diff/format-patch: refactor check for commit range
Currently, when called with exactly two arguments, `git range-diff`
tests for a literal `..` in each of the two. Likewise, the argument
provided via `--range-diff` to `git format-patch` is checked in the same
manner.
However, `<commit>^!` is a perfectly valid commit range, equivalent to
`<commit>^..<commit>` according to the `SPECIFYING RANGES` section of
gitrevisions[7].
In preparation for allowing more sophisticated ways to specify commit
ranges, let's refactor the check into its own function.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'range-diff.c')
| -rw-r--r-- | range-diff.c | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/range-diff.c b/range-diff.c index b9950f1..9b93e08 100644 --- a/range-diff.c +++ b/range-diff.c @@ -564,3 +564,8 @@ int show_range_diff(const char *range1, const char *range2, return res; } + +int is_range_diff_range(const char *arg) +{ + return !!strstr(arg, ".."); +} |