From: David Weinehall <tao@acc.umu.se>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Bill Nottingham <notting@redhat.com>,
Jeff Garzik <jeff@garzik.org>, Josh Boyer <jwboyer@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
jffs-dev@axis.com, David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH/RFC] Delete JFFS (version 1)
Date: Tue, 19 Dec 2006 11:56:08 +0100 [thread overview]
Message-ID: <20061219105608.GC19442@vasa.acc.umu.se> (raw)
In-Reply-To: <20061212172843.40edbaed@localhost.localdomain>
On Tue, Dec 12, 2006 at 05:28:43PM +0000, Alan wrote:
> On Tue, 12 Dec 2006 12:01:25 -0500
> Bill Nottingham <notting@redhat.com> wrote:
>
> > Jeff Garzik (jeff@garzik.org) said:
> > > It's always been the case that we remove Linux kernel code when the
> > > number of users (and more importantly, developers) drops to near-nil.
> >
> > So, drivers/net/3c501.c?
>
> I think 3c501.c is a case where putting in an "If you use this email ..
> or it will go away" might be a good idea indeed.
Maybe even: "the people who are using 3c501's - please chime up and we'll
donate better cards to you."
After all, 3c501 is one of the crappier pieces of network cards,
I feel sorry for the people using them...
Regards: David
--
/) David Weinehall <tao@acc.umu.se> /) Northern lights wander (\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\) http://www.acc.umu.se/~tao/ (/ Full colour fire (/
next prev parent reply other threads:[~2006-12-19 10:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 12:39 Jeff Garzik
2006-12-12 12:56 ` Josh Boyer
2006-12-12 13:02 ` Jeff Garzik
2006-12-12 13:06 ` Josh Boyer
2006-12-12 13:07 ` David Woodhouse
2006-12-12 13:09 ` Jeff Garzik
2006-12-12 17:01 ` Bill Nottingham
2006-12-12 17:20 ` Jeff Garzik
2006-12-12 17:28 ` Alan
2006-12-19 10:56 ` David Weinehall [this message]
2006-12-12 12:58 ` Jörn Engel
2006-12-12 17:53 ` Andrew Morton
2006-12-12 18:38 ` Josh Boyer
2006-12-12 21:49 ` Andreas Dilger
2006-12-13 7:06 ` Jörn Engel
2007-03-09 23:13 ` Stefan Monnier
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=20061219105608.GC19442@vasa.acc.umu.se \
--to=tao@acc.umu.se \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=jeff@garzik.org \
--cc=jffs-dev@axis.com \
--cc=jwboyer@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=notting@redhat.com \
/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
all inboxes | Powered by JetHome®