Re: Formatting problem send_mail in version 2.10.0

2 messages, 2 authors, 2016-10-12 · open the first message on its own page

Re: Formatting problem send_mail in version 2.10.0

From: Matthieu Moy <hidden>
Date: 2016-10-11 16:19:48

Larry Finger [off-list ref] 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/

Re: Formatting problem send_mail in version 2.10.0

From: Larry Finger <hidden>
Date: 2016-10-12 04:44:01

On 10/11/2016 11:18 AM, Matthieu Moy wrote:
Larry Finger [off-list ref] writes:
quoted
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?
This format is used in a patch for the kernel. When the patch is merged into 
mainline, stable@vger.kernel.org gets sent an E-mail with a copy of the original 
patch. Maintainers of the indicated systems then merge the patch with their 
stable version.
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).
I do not want it in the body of the message. I just want to pass a hint to the 
stable maintainer(s).

As noted earlier, this has worked for a very long time, and I think the previous 
behavior should be restored.

Larry

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help