From: Greg KH <greg@kroah.com>
To: John Cherry <cherry@osdl.org>
Cc: Mark Bellon <mbellon@mvista.com>, Pat Mochel <mochel@osdl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-hotplug-devel@lists.sourceforge.net,
cgl_discussion@osdl.org
Subject: Re: ANNOUNCE: User-space System Device Enumeration (uSDE)
Date: Tue, 28 Oct 2003 11:53:23 -0800 [thread overview]
Message-ID: <20031028195323.GA7822@kroah.com> (raw)
In-Reply-To: <1067370055.27022.29.camel@cherrytest.pdx.osdl.net>
On Tue, Oct 28, 2003 at 11:40:55AM -0800, John Cherry wrote:
> As Lars stated in an earlier email, "Competition is good, but only if
> they explore distinct approaches". It is a shame that much effort has
> been duplicated here on similar approaches. I'm not fully aware of the
> history behind the divergence, but it makes sense to enumerate NOW what
> is lacking in udev from a uSDE perspective.
I'm not aware of why there was a divergence in the first place either :)
As udev has been public for a long time now, would someone from Monta
Vista care to detail why they found udev lacking and deserving of a
duplicate effort?
> One objective of the carrier grade initiative is to prevent duplicate
> effort. Now that we have two implementations, let's get the
> issues/differences on the table and cooperatively move to convergence.
I'm trying :)
greg k-h
next prev parent reply other threads:[~2003-10-28 19:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 20:42 ANNOUNCE: User-space System Device Enumeration (uSDE) Mark Bellon
2003-10-27 21:49 ` Patrick Mochel
2003-10-27 23:09 ` Mark Bellon
2003-10-27 23:39 ` Greg KH
2003-10-28 17:47 ` Mark Bellon
2003-10-28 18:17 ` Greg KH
2003-10-28 19:40 ` John Cherry
2003-10-28 19:53 ` Greg KH [this message]
2003-10-28 17:16 ` Patrick Mochel
2003-10-28 18:12 ` Mark Bellon
2003-10-28 18:45 ` Chris Friesen
2003-10-28 18:48 ` Greg KH
2003-10-28 22:59 ` Andreas Jellinghaus
2003-10-29 1:59 ` Greg KH
2003-10-28 17:29 ` Lars Marowsky-Bree
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=20031028195323.GA7822@kroah.com \
--to=greg@kroah.com \
--cc=cgl_discussion@osdl.org \
--cc=cherry@osdl.org \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mbellon@mvista.com \
--cc=mochel@osdl.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