From: Matthieu Moy <Matthieu.Moy@univ-lyon1.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Payre Nathan <second.payre@gmail.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>,
ALBERTIN TIMOTHEE p1514771 <timothee.albertin@etu.univ-lyon1.fr>,
BENSOUSSAN--BOHM DANIEL p1507430
<daniel.bensoussan--bohm@etu.univ-lyon1.fr>,
Tom Russello <tom.russello@grenoble-inp.org>
Subject: Re: [PATCH 2/2] send-email: quote-email quotes the message body
Date: Wed, 01 Nov 2017 12:12:05 +0100 [thread overview]
Message-ID: <q7h9shdyw8vu.fsf@orange.lip.ens-lyon.fr> (raw)
In-Reply-To: <0db6387ef95b4fafbd70068be9e4f7c5@BPMBX2013-01.univ-lyon1.fr> (Junio C. Hamano's message of "Wed, 1 Nov 2017 06:40:00 +0000")
Junio C Hamano <gitster@pobox.com> writes:
> Hmmm. I have a strong suspicion that people want an option to
> trigger the feature from just 1/2 but not 2/2 some of the time.
> Sure, removing the unwanted lines in the compose editor may be easy,
> but it feels wasteful use of user's time to include the lines of
> text from the original only to have them removed.
So, that could be
git send-email --in-reply-to=message-id # message-id is not a file
=> existing behavior
git send-email --in-reply-to=file
=> populate To:, Cc:, In-Reply-To: and References:
git send-email --in-reply-to=file --quote
=> in addition to the above, include the quoted message in the body
(perhaps --quote should be --cite, I'm not sure which one looks best for
a native speaker)
This also leaves room for
git send-email --in-reply-to=message-id --fetch [--quote]
=> download the message body from e.g. public-inbox and do the same as
for --in-reply-to=file
(which doesn't have to be implemented now, but would be a nice-to-have
in the future)
--
Matthieu Moy
https://matthieu-moy.fr/
prev parent reply other threads:[~2017-11-01 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 22:34 [PATCH 0/2] New send-email option --quote-email Payre Nathan
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 [this message]
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=q7h9shdyw8vu.fsf@orange.lip.ens-lyon.fr \
--to=matthieu.moy@univ-lyon1.fr \
--cc=daniel.bensoussan--bohm@etu.univ-lyon1.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=second.payre@gmail.com \
--cc=timothee.albertin@etu.univ-lyon1.fr \
--cc=tom.russello@grenoble-inp.org \
/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).