From: Greg KH <gregkh@suse.de>
To: Joe Perches <joe@perches.com>
Cc: Pavel Machek <pavel@ucw.cz>,
"John W. Linville" <linville@tuxdriver.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] strip: move driver to staging
Date: Mon, 26 Oct 2009 12:17:40 -0700 [thread overview]
Message-ID: <20091026191740.GA31910@suse.de> (raw)
In-Reply-To: <1256584063.1865.118.camel@Joe-Laptop.home>
On Mon, Oct 26, 2009 at 12:07:43PM -0700, Joe Perches wrote:
> On Mon, 2009-10-26 at 11:48 -0700, Greg KH wrote:
> > On Mon, Oct 26, 2009 at 06:24:34PM +0100, Pavel Machek wrote:
> > > Anyway, for moving to staging, TODO file describing what needs to be
> > > fixed before it is brought back was listed as a requirement.
> > - A maintainer is needed to take ownership of this driver and
> > they must be willing to maintain and test any future api
> > changes needed.
>
> There are a lot of files in the tree without assigned maintainers.
> (want a list? ;)
>
> I think adding a requirement that files have maintainers before
> being added to not-staging is not a good thing.
>
> It is likely that strip could have be deleted without anyone caring.
Ok, then we can delete it, but I was trying to be nice here and provide
a way for people to "rescue" it with a nice announcement and grace
period.
Geesh, see what I get for being nice...
greg k-h
next prev parent reply other threads:[~2009-10-26 19:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 5:17 [PATCH 1/4] strip: move driver to staging John W. Linville
2009-10-20 5:17 ` [PATCH 2/4] arlan: " John W. Linville
[not found] ` <1256015830-12700-3-git-send-email-linville@tuxdriver.com>
2009-10-20 5:17 ` [PATCH 4/4] netwave: " John W. Linville
2009-10-27 20:36 ` Staging: " Greg KH
2009-10-27 21:05 ` John W. Linville
2009-10-27 22:12 ` Greg KH
2009-10-20 16:06 ` [PATCH 1/4] strip: " Randy Dunlap
2009-10-26 16:46 ` John W. Linville
2009-10-26 17:02 ` Randy Dunlap
2009-10-26 18:48 ` Greg KH
2009-10-23 16:10 ` Pavel Machek
2009-10-23 16:54 ` Alan Cox
2009-10-26 16:55 ` John W. Linville
2009-10-26 17:18 ` david
2009-10-26 17:43 ` John W. Linville
2009-10-26 18:47 ` Greg KH
2009-10-27 4:17 ` david
2009-10-27 5:21 ` David Miller
2009-10-27 8:34 ` Stefan Richter
2009-10-27 14:08 ` Greg KH
2009-10-27 18:39 ` david
2009-10-27 20:38 ` Greg KH
2009-10-27 21:13 ` John W. Linville
2009-10-27 21:32 ` Alan Cox
2009-10-26 17:24 ` Pavel Machek
2009-10-26 17:29 ` Alan Cox
2009-10-26 17:34 ` John W. Linville
2009-10-26 18:48 ` Greg KH
2009-10-26 19:07 ` Joe Perches
2009-10-26 19:17 ` Greg KH [this message]
2009-10-26 19:20 ` John W. Linville
2009-10-26 19:36 ` Greg KH
2009-10-26 20:06 ` 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=20091026191740.GA31910@suse.de \
--to=gregkh@suse.de \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=pavel@ucw.cz \
/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