public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Joe Perches <joe@perches.com>
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: Tue, 20 Aug 2013 20:36:27 -0500	[thread overview]
Message-ID: <1377048987.2737.89@driftwood> (raw)
In-Reply-To: <1377044556.2016.102.camel@joe-AO722> (from joe@perches.com on Tue Aug 20 19:22:36 2013)

On 08/20/2013 07:22:36 PM, Joe Perches wrote:
> On Tue, 2013-08-20 at 19:10 -0500, Rob Landley wrote:
> > The important question is does he want to handle patches that you're
> > flipping out about not going in before the next merge window because
> > they are SO IMPORTANT that the trivial tree must promote them out of
> > sequence.
> 
> You're misreading.  I see no flipping out here.
> 
> I'm simply saying that obvious defects should be
> corrected sooner rather than later.
> 
> 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.

I fetch his git and look at the log of the branch to see which of the  
documentation patches I forwarded are there. That said, there's no  
guarantee they'll go in from there because other maintainers often grab  
them and put them in through their trees.

> Jiri has not responded to this point.

He did. Twice.

> Silence about the status of patches that extends
> for months is not good.

He has a public git tree. It's listed in his MAINTAINERS entry. I've  
found that if a patch isn't in there, he hasn't picked it up yet. (I've  
been feeding Documentation patches through his tree, hence my interest  
in this thread.)

Rob

  reply	other threads:[~2013-08-21  1:36 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 [this message]
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=1377048987.2737.89@driftwood \
    --to=rob@landley.net \
    --cc=akpm@linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox