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

[PATCH 3/3] Expand git-send-email docs to mention format-patch options.

From
Thiago Perrotta <tbperrotta@gmail.com>
Date
Aug 2, 2021, 20:49 UTC
Message-ID
<20210802204953.229867-4-tbperrotta@gmail.com>
In-Reply-To
<20210802204953.229867-1-tbperrotta@gmail.com>

Currently git-send-email(1) does not make it explicit format-patch options are accepted.

Signed-off-by: Thiago Perrotta <tbperrotta@gmail.com>
---
 Documentation/git-send-email.txt | 2 ++
 1 file changed, 2 insertions(+)
diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt
index 3db4eab..05dd8de 100644
--- a/Documentation/git-send-email.txt
+++ b/Documentation/git-send-email.txt
@@ -42,6 +42,8 @@ and the "Subject:" of the message as the second line.
 OPTIONS
 -------
 
+Options from linkgit:git-format-patch[1] are also accepted.
+
 Composing
 ~~~~~~~~~
 
-- 
2.32.0
Previous: Thiago Perrotta
Message 4 of 4 in “git-send-email options and completion improvements”
  1. 0/3 git-send-email options and completion improvementsThiago Perrotta, Aug 2, 2021
  2. 1/3 Print newline for git-send-email --git-completion-helper.Thiago Perrotta, Aug 2, 2021
  3. 2/3 Move bash git-send-email completions to original script.Thiago Perrotta, Aug 2, 2021
  4. 3/3 Expand git-send-email docs to mention format-patch options.Thiago Perrotta, Aug 2, 2021

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.