diff options
| author |  Johannes Schindelin <johannes.schindelin@gmx.de> | 2021-01-27 16:37:22 +0000 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2021-01-27 22:01:49 -0800 |
| commit | 679b5916cdafdcfa9fb36c31dbf53d7e4aa0af0b (patch) | |
| tree | d3ad427618e272cc05cc4c8924f0ff3114612d04 /Documentation/diff-format.txt | |
| parent | The third batch (diff) | |
| download | tgif-679b5916cdafdcfa9fb36c31dbf53d7e4aa0af0b.tar.xz | |
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 'Documentation/diff-format.txt')
0 files changed, 0 insertions, 0 deletions