From: Willy Tarreau <w@1wt.eu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Stable queue is caught up on for 3.10, 3.14, 4.1, and 4.2-stable kernels
Date: Sun, 18 Oct 2015 08:05:25 +0200 [thread overview]
Message-ID: <20151018060525.GA31915@1wt.eu> (raw)
In-Reply-To: <20151018060237.GA32100@kroah.com>
On Sat, Oct 17, 2015 at 11:02:37PM -0700, Greg KH wrote:
> On Sun, Oct 18, 2015 at 07:56:06AM +0200, Willy Tarreau wrote:
> > Hi Greg,
> >
> > On Sat, Oct 17, 2015 at 07:09:52PM -0700, Greg KH wrote:
> > > Hi all,
> > >
> > > I've finally caught up on all pending patches for the above mentioned
> > > stable kernels that have either hit Linus's tree with a stable@ or
> > > fixes: marking, or have been emailed to the stable@ list requesting to
> > > be included.
> >
> > Impressed :-)
> >
> > I'm seeing that each series ends with patch (N-1)/N, so I think something
> > changed in your scripts, either N is wrong in which case we can ignore
> > this, or the last patch of each series was not sent.
> >
> > Could you please double-check ?
>
> I see it on my end, and I got the cc:. vger likes to reject some of the
> patches due to odd mime-encoding issues as it fights between git
> send-email and how it creates the patches. So maybe that was one of
> them, I know I got many bounces this time around.
yes indeed I've met this as well.
> I don't really know how to resolve this, sorry.
No problem, I wanted to be sure that you didn't break something in your
scripts.
Thanks!
Willy
prev parent reply other threads:[~2015-10-18 6:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 2:09 Stable queue is caught up on for 3.10, 3.14, 4.1, and 4.2-stable kernels Greg KH
2015-10-18 5:56 ` Willy Tarreau
2015-10-18 6:02 ` Greg KH
2015-10-18 6:05 ` Willy Tarreau [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151018060525.GA31915@1wt.eu \
--to=w@1wt.eu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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