From: Joe Perches <joe@perches.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>
Subject: Re: rfc: trivial patches and slow deaths?
Date: Mon, 19 Aug 2013 21:27:17 +0000 [thread overview]
Message-ID: <1376947637.2016.39.camel@joe-AO722> (raw)
In-Reply-To: <alpine.LNX.2.00.1308192315000.21654@pobox.suse.cz>
On Mon, 2013-08-19 at 23:22 +0200, Jiri Kosina wrote:
> On Mon, 19 Aug 2013, Joe Perches wrote:
>
> > This is a 7 line patch that corrects logging defects that has had no
> > reply from you for the last month.
> >
> > https://patchwork.kernel.org/patch/2833648/
>
> This hasn't missed any Linus' major release, as it has been submitted post
> 3.11 merge, right? (hint, that was Jul 4th).
>
> If this would miss *next* major Linus' release, I would accept your
> complaints. But this is definitely not the case.
You're suggesting this patch, which corrects obvious
defects, should miss 3.12 and go into 3.13?
I think that's wrong.
I think it should be in -next now. It's not.
What should any patch submitter expect about
visibility and/or knowledge of the applicability
of this sort of patch from trivial?
next prev parent reply other threads:[~2013-08-19 21:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 20:27 rfc: trivial patches and slow deaths? Joe Perches
2013-08-19 20:34 ` Jiri Kosina
2013-08-19 21:10 ` Joe Perches
2013-08-19 21:22 ` Jiri Kosina
2013-08-19 21:27 ` Joe Perches [this message]
2013-08-20 20:02 ` Rob Landley
2013-08-20 20:14 ` Joe Perches
2013-08-20 21:49 ` Rob Landley
2013-08-20 22:11 ` Joe Perches
2013-08-20 22:24 ` Andrew Morton
2013-08-20 22:49 ` Joe Perches
2013-08-21 0:10 ` Rob Landley
2013-08-21 0:22 ` Joe Perches
2013-08-21 1:36 ` Rob Landley
2013-08-21 4:10 ` Joe Perches
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=1376947637.2016.39.camel@joe-AO722 \
--to=joe@perches.com \
--cc=jkosina@suse.cz \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@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