summaryrefslogtreecommitdiff
path: root/range-diff.h
diff options
context:
space:
mode:
authorJohannes Schindelin <johannes.schindelin@gmx.de>2021-02-05 14:46:13 +0000
committerJunio C Hamano <gitster@pobox.com>2021-02-06 21:14:31 -0800
commit1e79f973266cfe0e3bab0e26e869b682078e457d (patch)
tree419e8d3df016350fa2867d2be741f90385b94fa4 /range-diff.h
parent3e6046edadf409537cc9e991d1df628fa96953ba (diff)
downloadgit-1e79f973266cfe0e3bab0e26e869b682078e457d.tar.gz
range-diff: offer --left-only/--right-only options
When comparing commit ranges, one is frequently interested only in one side, such as asking the question "Has this patch that I submitted to the Git mailing list been applied?": one would only care about the part of the output that corresponds to the commits in a local branch. To make that possible, imitate the `git rev-list` options `--left-only` and `--right-only`. This addresses https://github.com/gitgitgadget/git/issues/206 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'range-diff.h')
-rw-r--r--range-diff.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/range-diff.h b/range-diff.h
index 0bae6b0cb1..27c9adfd2b 100644
--- a/range-diff.h
+++ b/range-diff.h
@@ -9,6 +9,7 @@
struct range_diff_options {
int creation_factor;
unsigned dual_color:1;
+ unsigned left_only:1, right_only:1;
const struct diff_options *diffopt; /* may be NULL */
const struct strvec *other_arg; /* may be NULL */
};