summaryrefslogtreecommitdiff
path: root/t/t3206-range-diff.sh
diff options
context:
space:
mode:
authorEric Sunshine <sunshine@sunshineco.com>2018-07-22 09:57:14 (GMT)
committerJunio C Hamano <gitster@pobox.com>2018-08-14 21:27:04 (GMT)
commit2e6fd71a52f5bde1c4036b8b0c586ae446f620f8 (patch)
treef841048d434b7cbfa3fbe4e64d3c779bd27e8015 /t/t3206-range-diff.sh
parent31e2617a5f8fe1c114e72f058d1c035bbf77cffe (diff)
downloadgit-2e6fd71a52f5bde1c4036b8b0c586ae446f620f8.zip
git-2e6fd71a52f5bde1c4036b8b0c586ae446f620f8.tar.gz
git-2e6fd71a52f5bde1c4036b8b0c586ae446f620f8.tar.bz2
format-patch: extend --range-diff to accept revision range
When submitting a revised a patch series, the --range-diff option embeds a range-diff in the cover letter showing changes since the previous version of the patch series. The argument to --range-diff is a simple revision naming the tip of the previous series, which works fine if the previous and current versions of the patch series share a common base. However, it fails if the revision ranges of the old and new versions of the series are disjoint. To address this shortcoming, extend --range-diff to also accept an explicit revision range for the previous series. For example: git format-patch --cover-letter --range-diff=v1~3..v1 -3 v2 Signed-off-by: Eric Sunshine <sunshine@sunshineco.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t3206-range-diff.sh')
-rwxr-xr-xt/t3206-range-diff.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/t/t3206-range-diff.sh b/t/t3206-range-diff.sh
index dd854b6..3d7a2d8 100755
--- a/t/t3206-range-diff.sh
+++ b/t/t3206-range-diff.sh
@@ -142,7 +142,7 @@ test_expect_success 'changed message' '
test_cmp expected actual
'
-for prev in topic
+for prev in topic master..topic
do
test_expect_success "format-patch --range-diff=$prev" '
git format-patch --stdout --cover-letter --range-diff=$prev \