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

[PATCH] git-send-email.txt: move --format-patch paragraph to a proper location

From
Adeodato Simó <dato@net.com.org.es>
Date
Dec 27, 2008, 08:50 UTC
Message-ID
<1230367830-6114-1-git-send-email-dato@net.com.org.es>

When introducing --format-patch, its documentation was accidentally inserted in the middle of documentation for --validate.

Signed-off-by: Adeodato Simó <dato@net.com.org.es>
---
 Documentation/git-send-email.txt |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt
index 1278866..b69846e 100644
--- a/Documentation/git-send-email.txt
+++ b/Documentation/git-send-email.txt
@@ -197,12 +197,6 @@ Administering
 --[no-]validate::
 	Perform sanity checks on patches.
 	Currently, validation means the following:
-
---[no-]format-patch::
-	When an argument may be understood either as a reference or as a file name,
-	choose to understand it as a format-patch argument ('--format-patch')
-	or as a file name ('--no-format-patch'). By default, when such a conflict
-	occurs, git send-email will fail.
 +
 --
 		*	Warn of patches that contain lines longer than 998 characters; this
@@ -212,6 +206,12 @@ Administering
 Default is the value of 'sendemail.validate'; if this is not set,
 default to '--validate'.
 
+--[no-]format-patch::
+	When an argument may be understood either as a reference or as a file name,
+	choose to understand it as a format-patch argument ('--format-patch')
+	or as a file name ('--no-format-patch'). By default, when such a conflict
+	occurs, git send-email will fail.
+
 
 CONFIGURATION
 -------------
-- 
1.6.1.307.g07803
Next: Junio C Hamano
Message 1 of 2 in “git-send-email.txt: move --format-patch paragraph to a proper location”
  1. git-send-email.txt: move --format-patch paragraph to a proper locationAdeodato Simó, Dec 27, 2008
  2. Junio C HamanoDec 27, 2008

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.