From: Adrian Bunk <bunk@stusta.de>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Old api files, rewrite or delete?
Date: Fri, 5 Aug 2005 00:03:58 +0200 [thread overview]
Message-ID: <20050804220357.GG4029@stusta.de> (raw)
In-Reply-To: <42F20345.3020603@gmail.com>
On Thu, Aug 04, 2005 at 02:00:05PM +0200, Jiri Slaby wrote:
> Hi.
> I'm interested mainly in things that may be removed. I don't want to
> rewrite drivers, which nobody uses.
> Thanks for your opinion and knowledge about usage.
>...
There might be users for many of the listed drivers - even if there are
only very few.
And what do you really gain by removing drivers?
cu
Adrian
--
"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
next prev parent reply other threads:[~2005-08-04 22:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 12:00 Old api files, rewrite or delete? Jiri Slaby
2005-08-04 13:43 ` Russell King
2005-08-04 14:36 ` Jiri Slaby
2005-08-04 22:03 ` Adrian Bunk [this message]
2005-08-04 22:18 ` Jiri Slaby
2005-08-05 6:13 ` Jan Engelhardt
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=20050804220357.GG4029@stusta.de \
--to=bunk@stusta.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