git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v2 1/1] t3206-range-diff.sh: cover single-patch case

From
Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com>
Date
Sep 12, 2018, 14:31 UTC
Message-ID
<277a4d2bd8bcb20323f0a5a01ccdf431f3c08350.1536762661.git.gitgitgadget@gmail.com>
In-Reply-To
<pull.37.v2.git.gitgitgadget@gmail.com>
From: Derrick Stolee <dstolee@microsoft.com>

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@microsoft.com>
---
 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..6babc0e276 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 &&
+	test_i18ngrep "^Range-diff:$" actual
+'
+
 test_done
-- 
gitgitgadget
Previous: Derrick Stolee via GitGitGadget
Message 11 of 11 in “Add coverage for 'git format-patch --range-diff' single-patch case”
  1. 0/1 Add coverage for 'git format-patch --range-diff' single-patch caseDerrick Stolee via GitGitGadget, Sep 11, 2018
  2. 1/1 t3206-range-diff.sh: cover single-patch caseDerrick Stolee via GitGitGadget, Sep 11, 2018
  3. Junio C HamanoSep 11, 2018
  4. Junio C HamanoSep 11, 2018
  5. Stefan BellerSep 11, 2018
  6. Eric SunshineSep 11, 2018
  7. Derrick StoleeSep 12, 2018
  8. Derrick StoleeSep 11, 2018
  9. Eric SunshineSep 11, 2018
  10. 0/1 Add coverage for 'git format-patch --range-diff' single-patch caseDerrick Stolee via GitGitGadget, Sep 12, 2018
  11. 1/1 t3206-range-diff.sh: cover single-patch caseDerrick Stolee via GitGitGadget, Sep 12, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.