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

[PATCH v6 4/6] fast-import: test the new feature command

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Sep 2, 2009, 17:57 UTC
Message-ID
<1251914223-31435-5-git-send-email-srabbelier@gmail.com>
In-Reply-To
<1251914223-31435-4-git-send-email-srabbelier@gmail.com>

Test that an unknown feature causes fast-import to abort, and that a known feature is accepted.

Signed-off-by: Sverre Rabbelier <srabbelier@gmail.com>
---
 t/t9300-fast-import.sh |   20 ++++++++++++++++++++
 1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/t/t9300-fast-import.sh b/t/t9300-fast-import.sh
index 821be7c..564ed6b 100755
--- a/t/t9300-fast-import.sh
+++ b/t/t9300-fast-import.sh
@@ -1088,4 +1088,24 @@ INPUT_END
 test_expect_success 'P: fail on blob mark in gitlink' '
     test_must_fail git fast-import <input'
 
+###
+### series R (feature)
+###
+
+cat >input <<EOF
+feature no-such-feature-exists
+EOF
+
+test_expect_success 'R: abort on unsupported feature' '
+	test_must_fail git fast-import <input
+'
+
+cat >input <<EOF
+feature date-format=now
+EOF
+
+test_expect_success 'R: supported feature is accepted' '
+	git fast-import <input
+'
+
 test_done
-- 
1.6.4.16.g72c66.dirty
Previous: Sverre RabbelierNext: Sverre Rabbelier
Message 5 of 10 in “fast-import: add new feature and mark command”
  1. 0/6 fast-import: add new feature and mark commandSverre Rabbelier, Sep 2, 2009
  2. 1/6 fast-import: put option parsing code in separate functionsSverre Rabbelier, Sep 2, 2009
  3. 2/6 fast-import: put marks reading in it's own functionSverre Rabbelier, Sep 2, 2009
  4. 3/6 fast-import: add feature commandSverre Rabbelier, Sep 2, 2009
  5. 4/6 fast-import: test the new feature commandSverre Rabbelier, Sep 2, 2009
  6. 5/6 fast-import: add option commandSverre Rabbelier, Sep 2, 2009
  7. 6/6 fast-import: test the new option commandSverre Rabbelier, Sep 2, 2009
  8. Junio C HamanoSep 3, 2009
  9. Sverre RabbelierSep 3, 2009
  10. Ian ClatworthySep 4, 2009

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.