From: Rob Love <rml@ximian.com>
To: hzhong@cisco.com
Cc: "'Jari Soderholm'" <Jari.Soderholm@edu.stadia.fi>,
linux-kernel@vger.kernel.org
Subject: RE: DEVFS is very good compared to UDEV
Date: Tue, 23 Dec 2003 18:03:23 -0500 [thread overview]
Message-ID: <1072220603.8404.1.camel@fur> (raw)
In-Reply-To: <008901c3c9a8$97ac5c50$ca41cb3f@amer.cisco.com>
On Tue, 2003-12-23 at 18:00, Hua Zhong wrote:
> Me neither :-) and when he is not flaming me (which I have not got the
> chance yet), it's fun to read. But I hate him, you know, because I now
> tend to be influenced by the way he (and several others on this list)
> writes emails, and that's not nice in a corporate environment!!
You should not hate anyone. But especially not Al.
> It's just my impression that around that time core developers had
> decided to replace devfs with a new model. If I were in ths same shoes,
> I would probably also stop maintaining it. Then 2 years later when
> somebody asks, the reason to replace my code shouldn't be
> "unmaintained". Just the technical reasons should be enough. :-)
Sure. But, it is unmaintained today, regardless of why, and that is a
factor in deciding how to proceed.
Rob Love
next prev parent reply other threads:[~2003-12-23 23:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 21:20 DEVFS is very good compared to UDEV Jari Soderholm
2003-12-23 21:50 ` Stan Bubrouski
2003-12-23 22:01 ` Rob Love
2003-12-23 22:21 ` Hua Zhong
2003-12-23 22:30 ` Rob Love
2003-12-23 23:00 ` Hua Zhong
2003-12-23 23:03 ` Rob Love [this message]
2003-12-23 23:14 ` Greg KH
2003-12-23 23:26 ` viro
2003-12-24 0:00 ` Mike Fedyk
2003-12-23 23:03 ` grundig
2003-12-23 23:05 ` viro
2003-12-24 2:24 ` Paul Jackson
2003-12-23 22:24 ` Felipe Alfaro Solana
2003-12-27 11:57 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2003-12-24 3:33 Albert Cahalan
2003-12-24 18:40 ` Theodore Ts'o
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=1072220603.8404.1.camel@fur \
--to=rml@ximian.com \
--cc=Jari.Soderholm@edu.stadia.fi \
--cc=hzhong@cisco.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