From: Joe Perches <joe@perches.com>
To: Rob Landley <rob@landley.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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: Wed, 21 Aug 2013 04:10:07 +0000 [thread overview]
Message-ID: <1377058207.1936.6.camel@joe-AO722> (raw)
In-Reply-To: <1377048987.2737.89@driftwood>
On Tue, 2013-08-20 at 20:36 -0500, Rob Landley wrote:
> On 08/20/2013 07:22:36 PM, Joe Perches wrote:
> > I'm also saying that the trivial tree should
> > have some visibility about whether or not a
> > patch or series will be handled by the trivial
> > maintainer or not.
[]
> > Jiri has not responded to this point.
> He did. Twice.
Not really.
> > Silence about the status of patches that extends
> > for months is not good.
>
> He has a public git tree.
Yes, I know.
> I've found that if a patch isn't in there, he hasn't picked
> it up yet.
It's the visibility of if/yet/when for the trivial
patches submitted and unresponded to that's the question.
And no, Jiri hasn't responded with any intention of
making any such scheme public.
I think a public patchwork queue like netdev's could
work reasonably well.
http://patchwork.ozlabs.org/project/netdev/list/
prev parent reply other threads:[~2013-08-21 4:10 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
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 [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=1377058207.1936.6.camel@joe-AO722 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=jkosina@suse.cz \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
/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