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

[PATCH] Remove "unsure" for --message in subtree doc.

From
Danny Lin <danny0838@gmail.com>
Date
Aug 14, 2020, 14:53 UTC
Message-ID
<20200814145344.2413-1-danny0838@gmail.com>
It is definitely clear that --message is valid for add, merge and pull.
Signed-off-by: Danny Lin <danny0838@gmail.com>
---
 contrib/subtree/git-subtree.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/subtree/git-subtree.txt b/contrib/subtree/git-subtree.txt
index 352deda69d..47e2c611fe 100644
--- a/contrib/subtree/git-subtree.txt
+++ b/contrib/subtree/git-subtree.txt
@@ -139,7 +139,7 @@ OPTIONS
 
 -m <message>::
 --message=<message>::
-	This option is only valid for add, merge and pull (unsure).
+	This option is only valid for add, merge and pull.
 	Specify <message> as the commit message for the merge commit.
 
 

-- 
2.28.0.windows.1
Next: Junio C Hamano
Message 1 of 6 in “Remove "unsure" for --message in subtree doc.”
  1. Remove "unsure" for --message in subtree doc.Danny Lin, Aug 14, 2020
  2. Junio C HamanoAug 14, 2020
  3. Danny LinAug 15, 2020
  4. Revise supported options for --message in subtree doc.Danny Lin, Aug 15, 2020
  5. Junio C HamanoAug 17, 2020
  6. contrib/subtree: fix "unsure" for --message in the documentDanny Lin, Aug 18, 2020

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.