public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Dave Jones <davej@redhat.com>, Jiri Slaby <jirislaby@gmail.com>,
	Andrew Morton <akpm@osdl.org>,
	Rolf Eike Beer <eike-kernel@sf-tec.de>
Subject: Re: [PATCH] Removing maintainer's bad e-mails
Date: Tue, 9 Aug 2005 02:56:59 +0200	[thread overview]
Message-ID: <20050809005659.GT4006@stusta.de> (raw)
In-Reply-To: <20050809003140.GJ7667@kurtwerks.com>

On Mon, Aug 08, 2005 at 08:31:40PM -0400, Kurt Wall wrote:
> On Tue, Aug 09, 2005 at 12:49:17AM +0200, Adrian Bunk took 42 lines to write:
> > On Mon, Aug 08, 2005 at 02:33:00PM -0400, Dave Jones wrote:
> > > 
> > > You may as well change the S: to unmaintained whilst
> > > you're there, it hasn't seen any updates in a long time,
> > > and still uses several out-of-date SCSI APIs.
> > 
> > Or he could completely remove the entry.
> > 
> > We don't have entries for every single unmaintained driver, and the 
> > smaller MAINTAINERS is the higher is the possibility of not missing a 
> > relevant entry when checking whom to send an email.
> 
> Hmm, so if a subsystem or driver (more drivers, I should think) lacks
> an entry in MAINTAINERS, is it then reasonable to assume that it is
> unmaintained? If not, perhaps creating a separate list of unmaintained
> subsystems and/or drivers is prudent?

For unmaintained drivers or drivers maintained by the subsystem 
maintainers (which can be the reason why there's no entry for this 
driver) contact the subsystem maintainer.

Unmaintained subsystems are a problem.

I've already started contacting subsystem maintainers that seem to be 
inactive, and I have some restructuring of MAINTAINERS (tree structure 
with drivers behind subsystems) on my TODO list.

> Kurt

cu
Adrian

BTW: Please don't remove people from the Cc when answering.

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2005-08-09  0:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07 23:50 [PATCH] Removing maintainer's bad e-mails Jiri Slaby
2005-08-08 18:33 ` Dave Jones
2005-08-08 22:49   ` Adrian Bunk
2005-08-08 23:54     ` Jiri Slaby
2005-08-09  0:31     ` Kurt Wall
2005-08-09  0:56       ` Adrian Bunk [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=20050809005659.GT4006@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=eike-kernel@sf-tec.de \
    --cc=jirislaby@gmail.com \
    --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