[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100422201748.GB26924@suse.de>
Date: Thu, 22 Apr 2010 13:17:48 -0700
From: Greg KH <gregkh@...e.de>
To: Randy Dunlap <rdunlap@...otime.net>
Cc: "John W. Linville" <linville@...driver.com>,
Olivier Galibert <galibert@...ox.com>,
Joe Perches <joe@...ches.com>, devel@...verdev.osuosl.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: What's the staging review and acceptance process?
On Thu, Apr 22, 2010 at 01:06:16PM -0700, Randy Dunlap wrote:
> John W. Linville wrote:
> > On Thu, Apr 22, 2010 at 08:42:45AM +0200, Olivier Galibert wrote:
> >> On Wed, Apr 21, 2010 at 11:12:42PM -0700, Greg KH wrote:
> >>> On Wed, Apr 21, 2010 at 10:55:18PM -0700, Joe Perches wrote:
> >>>> Not really, patchwork shows status immediately.
> >>> Immediately when someone does something with it, right? So, the same as
> >>> my development cycle?
> >> I guess the main difference is that patchwork allows one contributor
> >> to see that his patch has just not been checked yet, vs. missed/lost.
> >
> > In Greg's defense, I find patchwork to be fairly unwieldy (which is
> > why I don't use it). It is certainly possible that I am missing some
> > key feature, but my limited experience with it suggested to me that all
> > the clicky-clicky stuff required to deal with the individual messages
> > queued in patchwork nearly doubled my time overhead associated with
> > merging patches.
>
>
> Just from a patch submitter perspective, I'd like to see some kind of
> response. I can believe what you say about patchwork, so I wouldn't
> advocate it.
>
> I agree to Joe's perspective that Greg is overbooked regarding time.
> I think that this is an ongoing problem, not just a current one that
> will go away, so for me, the question is what is Greg willing to do
> about it?
Greg is not going to take up 3 months of his life and sell and buy a
house and move.
Seriously, that took up all of my "free" time, and it's now over, and I
am catching up on things, give me a short ammount of time please.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists