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

[PATCH 2/3] Document long options '--message=<msg>' and '--no-commit'

From
Jakub Narebski <jnareb@gmail.com>
Date
Jul 12, 2007, 23:54 UTC
Message-ID
<11842844531700-git-send-email-jnareb@gmail.com>
In-Reply-To
<11842844481113-git-send-email-jnareb@gmail.com>

Document that '--message=<msg>' is long version of '-m <msg>' in git-commit, and that '--no-checkout' is long version of '-n' in git-clone.

Signed-off-by: Jakub Narebski <jnareb@gmail.com>
---
This patch was silently skipped in the 11 patches long series
of documenting undocumented long options
  "[PATCH 00/11] Document missing options"
(or rather two patches which are concatenated into this one).
 Documentation/git-clone.txt  |    1 +
 Documentation/git-commit.txt |    2 +-
 2 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
index 2f39864..a0a10e3 100644
--- a/Documentation/git-clone.txt
+++ b/Documentation/git-clone.txt
@@ -64,6 +64,7 @@ OPTIONS
 	Operate quietly.  This flag is passed to "rsync" and
 	"git-fetch-pack" commands when given.
 
+--no-checkout::
 -n::
 	No checkout of HEAD is performed after the clone is complete.
 
diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt
index 53a7bb0..352a494 100644
--- a/Documentation/git-commit.txt
+++ b/Documentation/git-commit.txt
@@ -71,7 +71,7 @@ OPTIONS
 	Override the author name used in the commit.  Use
 	`A U Thor <author@example.com>` format.
 
--m <msg>::
+-m <msg>|--message=<msg>::
 	Use the given <msg> as the commit message.
 
 -s|--signoff::
-- 
1.5.2.2
Previous: Jakub NarebskiNext: Jakub Narebski
Message 2 of 3 in “Document GIT_MERGE_VERBOSITY environmental variable”
  1. 1/3 Document GIT_MERGE_VERBOSITY environmental variableJakub Narebski, Jul 12, 2007
  2. 2/3 Document long options '--message=<msg>' and '--no-commit'Jakub Narebski, Jul 12, 2007
  3. 3/3 Document git commit --untracked-files and --verboseJakub Narebski, Jul 12, 2007

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.