From: Jim Nelson <james4765@verizon.net>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] remove obsolete Computone MAINTAINERS entry (fwd)
Date: Sat, 20 Nov 2004 10:06:17 -0500 [thread overview]
Message-ID: <419F5D69.2080407@verizon.net> (raw)
In-Reply-To: <20041120125017.GB2829@stusta.de>
Adrian Bunk wrote:
> On Fri, Nov 19, 2004 at 07:47:35PM -0800, Andrew Morton wrote:
>
>>Adrian Bunk <bunk@stusta.de> wrote:
>>
>>>I'm not sure whether it makes sense to list the previous maintainers for
>>> orphaned code, but if such entries contain buouncing mail addresses it's
>>> IMHO time to simply remove them.
>>>
>>>...
>>> -M: Michael H. Warfield <mhw@wittsend.com>
>>
>>wittsend.com is still there and Michael still runs it.
>
>
> At least the listed mailing list is defunct:
>
> <linux-computone@lazuli.wittsend.com>:
> Sorry, I wasn't able to establish an SMTP connection. (#4.4.1)
> I'm not going to try again; this message has been in the queue too long.
>
>
> And to be honest, I don't see that much value in shiping entries in
> MAINTAINERS for people who have reseigned as maintainers.
>
>
> cu
> Adrian
>
If someone is willing to step up to the plate and get the driver working again, it
would be better to have the contact information for the old maintainer available
in a centralized location. Plus, anyone who tries the driver and finds it busted
can look in the MAINTAINERS file and find out that it's not being fixed, instead
of it being one of those drivers that has no defined maintainer (I've run across a
few).
After all, we do have to be honest about unmaintained drivers - rather than hiding
broken code. Honestly, it's better to define who's responsible for an area of
code, even if it no longer works.
My $0.02.
Jim
next prev parent reply other threads:[~2004-11-20 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-20 0:25 [2.6 patch] remove obsolete Computone MAINTAINERS entry (fwd) Adrian Bunk
2004-11-20 3:47 ` Andrew Morton
2004-11-20 12:50 ` Adrian Bunk
2004-11-20 15:06 ` Jim Nelson [this message]
2004-11-20 17:48 ` Adrian Bunk
2004-12-20 19:15 ` Michael H. Warfield
2005-01-01 17:28 ` Adrian Bunk
2005-01-18 1:56 ` Michael H. Warfield
2005-02-02 19:52 ` [2.6 patch] update Computone MAINTAINERS entry Adrian Bunk
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=419F5D69.2080407@verizon.net \
--to=james4765@verizon.net \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--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