From: Payre Nathan <second.payre@gmail.com>
To: git@vger.kernel.org
Cc: matthieu.moy@univ-lyon1.fr, timothee.albertin@etu.univ-lyon1.fr,
daniel.bensoussan--bohm@etu.univ-lyon1.fr,
Payre Nathan <nathan.payre@etu.univ-lyon1.fr>
Subject: [PATCH 0/2] New send-email option --quote-email
Date: Mon, 30 Oct 2017 23:34:42 +0100 [thread overview]
Message-ID: <20171030223444.5052-1-nathan.payre@etu.univ-lyon1.fr> (raw)
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 reply other threads:[~2017-10-30 22:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 22:34 Payre Nathan [this message]
2017-10-30 22:34 ` [PATCH 1/2] quote-email populates the fields Payre Nathan
2017-11-01 2:44 ` Junio C Hamano
2017-11-09 8:49 ` Nathan PAYRE
[not found] ` <607ed87207454d1098484b0ffbc6916f@BPMBX2013-01.univ-lyon1.fr>
2017-11-01 11:04 ` Matthieu Moy
2017-11-01 18:12 ` Stefan Beller
2017-10-30 22:34 ` [PATCH 2/2] send-email: quote-email quotes the message body Payre Nathan
2017-11-01 6:40 ` Junio C Hamano
[not found] ` <0db6387ef95b4fafbd70068be9e4f7c5@BPMBX2013-01.univ-lyon1.fr>
2017-11-01 11:12 ` Matthieu Moy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171030223444.5052-1-nathan.payre@etu.univ-lyon1.fr \
--to=second.payre@gmail.com \
--cc=daniel.bensoussan--bohm@etu.univ-lyon1.fr \
--cc=git@vger.kernel.org \
--cc=matthieu.moy@univ-lyon1.fr \
--cc=nathan.payre@etu.univ-lyon1.fr \
--cc=timothee.albertin@etu.univ-lyon1.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).