From: Rob Landley <rob@landley.net>
To: Joe Perches <joe@perches.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>
Subject: Re: rfc: trivial patches and slow deaths?
Date: Tue, 20 Aug 2013 20:02:24 +0000 [thread overview]
Message-ID: <1377028944.2737.75@driftwood> (raw)
In-Reply-To: <1376947637.2016.39.camel@joe-AO722> (from joe@perches.com on Mon Aug 19 16:27:17 2013)
On 08/19/2013 04:27:17 PM, Joe Perches wrote:
> 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.
Correcting obvious defects, which can't wait a release, is "trivial"
now, is it?
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Landley <rob@landley.net>
To: Joe Perches <joe@perches.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>
Subject: Re: rfc: trivial patches and slow deaths?
Date: Tue, 20 Aug 2013 15:02:24 -0500 [thread overview]
Message-ID: <1377028944.2737.75@driftwood> (raw)
In-Reply-To: <1376947637.2016.39.camel@joe-AO722> (from joe@perches.com on Mon Aug 19 16:27:17 2013)
On 08/19/2013 04:27:17 PM, Joe Perches wrote:
> 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.
Correcting obvious defects, which can't wait a release, is "trivial"
now, is it?
Rob
next prev parent reply other threads:[~2013-08-20 20:02 UTC|newest]
Thread overview: 30+ 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:27 ` Joe Perches
2013-08-19 20:34 ` Jiri Kosina
2013-08-19 20:34 ` Jiri Kosina
2013-08-19 21:10 ` Joe Perches
2013-08-19 21:10 ` Joe Perches
2013-08-19 21:22 ` Jiri Kosina
2013-08-19 21:22 ` Jiri Kosina
2013-08-19 21:27 ` Joe Perches
2013-08-19 21:27 ` Joe Perches
2013-08-20 20:02 ` Rob Landley [this message]
2013-08-20 20:02 ` Rob Landley
2013-08-20 20:14 ` Joe Perches
2013-08-20 20:14 ` Joe Perches
2013-08-20 21:49 ` Rob Landley
2013-08-20 21:49 ` Rob Landley
2013-08-20 22:11 ` Joe Perches
2013-08-20 22:11 ` Joe Perches
2013-08-20 22:24 ` Andrew Morton
2013-08-20 22:24 ` Andrew Morton
2013-08-20 22:49 ` Joe Perches
2013-08-20 22:49 ` Joe Perches
2013-08-21 0:10 ` Rob Landley
2013-08-21 0:10 ` Rob Landley
2013-08-21 0:22 ` Joe Perches
2013-08-21 0:22 ` Joe Perches
2013-08-21 1:36 ` Rob Landley
2013-08-21 1:36 ` Rob Landley
2013-08-21 4:10 ` Joe Perches
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=1377028944.2737.75@driftwood \
--to=rob@landley.net \
--cc=jkosina@suse.cz \
--cc=joe@perches.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.