From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Grzegorz Kulewski <kangur@polcom.net>
Cc: linux-hotplug-devel@vger.kernel.org, greg@kroach.com,
linux-kernel@vger.kernel.org
Subject: Re: [QUESTION/PROPOSAL] udev (fwd)
Date: Wed, 03 Mar 2004 14:41:21 -0500 [thread overview]
Message-ID: <404634E1.6020703@nortelnetworks.com> (raw)
In-Reply-To: Pine.LNX.4.58.0403032023090.1319@alpha.polcom.net
Grzegorz Kulewski wrote:
> What You think about it?
I think you should use google before posting here.
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2004-03-03 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 19:27 [QUESTION/PROPOSAL] udev (fwd) Grzegorz Kulewski
2004-03-03 19:40 ` Tim Hockin
2004-03-03 20:51 ` Grzegorz Kulewski
2004-03-03 22:10 ` Tim Hockin
2004-03-03 19:41 ` Chris Friesen [this message]
2004-03-03 20:04 ` Felipe Alfaro Solana
2004-03-03 21:08 ` Greg KH
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=404634E1.6020703@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=greg@kroach.com \
--cc=kangur@polcom.net \
--cc=linux-hotplug-devel@vger.kernel.org \
--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