From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: stable@vger.kernel.org
Subject: Re: Missing -stable review patch mails
Date: Sun, 3 May 2015 11:03:11 +0200 [thread overview]
Message-ID: <20150503090311.GA21553@kroah.com> (raw)
In-Reply-To: <1430641739@msgid.manchmal.in-ulm.de>
On Sun, May 03, 2015 at 10:36:52AM +0200, Christoph Biedl wrote:
> Hi Greg,
>
> it seems several mails containing individual patches for -stable
> review did not get through. About the current round, the following
> mails are missing:
>
> PATCH 3.10 10/65
>
> PATCH 3.14 14/92
>
> PATCH 3.19 027/177
> PATCH 3.19 033/177
> PATCH 3.19 047/177
> PATCH 3.19 095/177
> PATCH 3.19 097/177
>
> PATCH 4.0 014/220
> PATCH 4.0 032/220
> PATCH 4.0 052/220
> PATCH 4.0 097/220
> PATCH 4.0 120/220
> PATCH 4.0 122/220
> PATCH 4.0 171/220
> PATCH 4.0 190/220
> PATCH 4.0 203/220
>
> Since they don't show up in gmane.linux.kernel.stable either, I reckon
> they got lost rather early on their way. This is not the first time,
> in the previous cycle, nine of 96 mails for 3.14 are missing, too.
>
> Can you please check mail logs or whatever?
This is a known issue of git and vger.kernel.org not liking to agree on
how to properly encode some utf-8 emails. vger rejects them because
they are not formatted "properly", yet I don't know what to do with git
to make that work "properly". It's been this way for a few years now,
and after trying to fix it once a while ago, I gave up as I didn't have
enough time to look into it...
sorry,
greg k-h
next prev parent reply other threads:[~2015-05-03 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 8:36 Missing -stable review patch mails Christoph Biedl
2015-05-03 8:57 ` Willy Tarreau
2015-05-03 9:03 ` Greg Kroah-Hartman [this message]
2015-05-04 20:50 ` Ben Hutchings
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150503090311.GA21553@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox