On Tue, Sep 11, 2018 at 1:21 PM Derrick Stolee via GitGitGadget
<gitgitgadget@xxxxxxxxx> wrote:
>
> From: Derrick Stolee <dstolee@xxxxxxxxxxxxx>
>
> The commit 40ce4160 "format-patch: allow --range-diff to apply to
> a lone-patch" added the ability to see a range-diff as commentary
> after the commit message of a single patch series (i.e. [PATCH]
> instead of [PATCH X/N]). However, this functionality was not
> covered by a test case.
>
> Add a simple test case that checks that a range-diff is written as
> commentary to the patch.
>
> Signed-off-by: Derrick Stolee <dstolee@xxxxxxxxxxxxx>
> ---
> t/t3206-range-diff.sh | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/t/t3206-range-diff.sh b/t/t3206-range-diff.sh
> index 3d7a2d8a4d..05ef3263d2 100755
> --- a/t/t3206-range-diff.sh
> +++ b/t/t3206-range-diff.sh
> @@ -154,4 +154,9 @@ do
> '
> done
>
> +test_expect_success 'format-patch --range-diff as commentary' '
> + git format-patch --stdout --range-diff=HEAD~1 HEAD~1 >actual &&
This is an interesting use of range-diff, as it basically tells us
"Range-diff: This is a new patch", but it works to make sure
there is a range diff section. (I shortly wondered if we would
ever omit the range diff for "obvious" cases or word it differently)
> + grep -A 1 -e "\-\-\-" actual | grep "Range-diff:"
So the first grep finds the three dashes, presumably those
after the commit message/ but others as well, e.g. in
--- a/<path>
+++ b/<path>
and then the second grep should find the string "Range-diff".
By having the greps chained with a pipe, only one return
code can be delivered to the test suite, and as we get the last
commands return code, we get reported if we found the string
in the preselected part.
I was wondering if we could get away with just one command to
check for that multi line pattern
sed -n -e '/---/,/^Range/p' actual
seems to detect that pattern, and prints from there on to the
rest of the file.
> +'
> +
> test_done
> --
> gitgitgadget
