linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Linux-hotplug needs an official maintainer.  Am I right?
Date: Tue, 16 Jan 2001 16:29:34 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-97966247015451@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97963444801580@msgid-missing>

On Tue, Jan 16, 2001 at 12:44:08AM -0800, Miles Lane wrote:
> 
> Since the hotplug implementation effort will include some
> ongoing general architecture work in addition to bus-specific
> work, perhaps we need a maintainer for the generic pieces, 
> while the bus-specific patches get routed through the bus
> maintainers.  Does this make sense?

If David doesn't want to do it, I'll volunteer.  He has done the most
work on it so far and deserves it.

However, remember that the maintainer tends to have development time
decrease, just ask Randy about being the USB maintainer :)

Also this looks like more of a coordination job, as all of the
individual pieces are all covered by other people, and the main job will
be notifying the current maintainers, and getting their buy in.

thanks, 

greg k-h

-- 
greg@(kroah|wirex).com

_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2001-01-16 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-16  8:44 Linux-hotplug needs an official maintainer. Am I right? Miles Lane
2001-01-16 16:29 ` Greg KH [this message]
2001-01-17  4:20 ` David Brownell
2001-01-17  4:50 ` Jeff Garzik
2001-01-17  4:57 ` Adam J. Richter
2001-01-17  7:37 ` David Hinds

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=marc-linux-hotplug-97966247015451@msgid-missing \
    --to=greg@kroah.com \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).