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

[PATCH 0/2] New send-email option --quote-email

From
PNPayre Nathan <second.payre@gmail.com>
Date
Oct 30, 2017, 22:34 UTC
Message-ID
<20171030223444.5052-1-nathan.payre@etu.univ-lyon1.fr>
Those patches implements a new --quote-email=<file> option.

Typical use case: the user receives a bug report by email and replies with a patch. Before this patch, to make a proper reply, the user had to perform several steps manually using "git send-email":

* Add --in-reply-to=<message_id> to the command-line for proper
  threading.
* Include the original recipients of the message using --to and --cc.
* Copy and prefix the original message with '> ' in the "below triple
  dash" part of the patch.

This patch allows send-email to do most of the job for the user, who can now save the email to a file and use:

  git send-email --quote-email=<file>

"To" and "Cc" will be added automaticaly and the email quoted. It's possible to edit the email before sending with --compose.

Based-on-patch-by: Tom Russello <tom.russello@grenoble-inp.org>
Signed-off: Nathan Payre <nathan.payre@etu.univ-lyon1.fr>
Signed-off: Matthieu Moy <matthieu.moy@univ-lyon1.fr>
Tom Russello (2):
  quote-email populates the fields
  send-email: quote-email quotes the message body
 Documentation/git-send-email.txt |   5 ++
 git-send-email.perl              | 146 +++++++++++++++++++++++++++++++++++++--
 t/t9001-send-email.sh            | 134 ++++++++++++++++++++++++-----------
 3 files changed, 240 insertions(+), 45 deletions(-)
-- 
2.14.2
Next: Payre Nathan
Message 1 of 9 in “New send-email option --quote-email”
  1. 0/2 New send-email option --quote-emailPayre Nathan, Oct 30, 2017
  2. 1/2 quote-email populates the fieldsPayre Nathan, Oct 30, 2017
  3. Junio C HamanoNov 1, 2017
  4. Nathan PAYRENov 9, 2017
  5. 2/2 send-email: quote-email quotes the message bodyPayre Nathan, Oct 30, 2017
  6. Junio C HamanoNov 1, 2017
  7. Matthieu MoyNov 1, 2017
  8. Stefan BellerNov 1, 2017
  9. Matthieu MoyNov 1, 2017

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.