From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Jeff King <peff@peff.net>,
Mathieu Lienard--Mayor <Mathieu.Lienard--Mayor@ensimag.imag.fr>,
Jorge Juan Garcia Garcia
<Jorge-Juan.Garcia-Garcia@ensimag.imag.fr>,
Remi Lespinet <remi.lespinet@ensimag.grenoble-inp.fr>,
git@vger.kernel.org
Subject: Re: Formatting problem send_mail in version 2.10.0
Date: Tue, 11 Oct 2016 18:18:47 +0200 [thread overview]
Message-ID: <vpq4m4iamfs.fsf@anie.imag.fr> (raw)
In-Reply-To: <45cfc4e5-c30e-19cb-ec3e-407ceb4e3ad5@lwfinger.net> (Larry Finger's message of "Tue, 11 Oct 2016 10:42:04 -0500")
Larry Finger <Larry.Finger@lwfinger.net> writes:
> That added information at the end is intended to be passed on to the
> stable group. In this case, the patch needs to be applied to kernel
> versions 4.8 and later.
OK, but where do people fetch this information from?
When you use git send-email, the content of the Cc: trailers ends up
both in the body of the message and in the Cc: field of the same
message.
If you need the mention to appear in the body of the message, then using
parenthesis is fine: git send-email won't remove it (more precisely,
"send-email" will call "format-patch" which won't remove it).
Not an objection to patching send-email anyway, but if there's a simple
and RFC-compliant way to do what you're looking for, we can as well use
it (possibly in addition to patching).
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2016-10-11 16:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 21:00 Formatting problem send_mail in version 2.10.0 Larry Finger
2016-10-10 21:48 ` Jeff King
2016-10-10 21:57 ` Jeff King
2016-10-10 23:35 ` Larry Finger
2016-10-10 23:43 ` Jeff King
2016-10-11 7:39 ` Matthieu Moy
2016-10-11 15:42 ` Larry Finger
2016-10-11 16:18 ` Matthieu Moy [this message]
2016-10-12 4:28 ` Larry Finger
2016-10-12 7:36 ` Matthieu Moy
2016-10-12 15:27 ` Larry Finger
2016-10-12 15:40 ` Matthieu Moy
2016-10-12 15:40 ` Larry Finger
2016-10-12 15:45 ` Matthieu Moy
2016-10-12 15:59 ` Larry Finger
2016-10-12 20:53 ` Junio C Hamano
2016-10-12 23:13 ` Jeff King
2016-10-13 5:37 ` Matthieu Moy
2016-10-13 5:47 ` [PATCH] parse_mailboxes: accept extra text after <...> address Matthieu Moy
2016-10-13 15:33 ` Formatting problem send_mail in version 2.10.0 Kevin Daudt
2016-10-13 16:05 ` Matthieu Moy
2016-10-13 5:32 ` Matthieu Moy
2016-10-14 17:04 ` Junio C Hamano
2016-10-11 16:02 ` Jeff King
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=vpq4m4iamfs.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=Jorge-Juan.Garcia-Garcia@ensimag.imag.fr \
--cc=Larry.Finger@lwfinger.net \
--cc=Mathieu.Lienard--Mayor@ensimag.imag.fr \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=remi.lespinet@ensimag.grenoble-inp.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).