From: Greg KH <greg@kroah.com>
To: "Jonathan A. George" <JAGeorge@greshamstorage.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6 udev capability question
Date: Tue, 7 Oct 2003 13:24:12 -0700 [thread overview]
Message-ID: <20031007202412.GF2670@kroah.com> (raw)
In-Reply-To: <3F831AAB.9040000@greshamstorage.com>
On Tue, Oct 07, 2003 at 02:57:31PM -0500, Jonathan A. George wrote:
> >Will do. Why did you not ask this there in the first place? Sending
> >email directly to developers isn't the nicest thing to do:
> > http://www.arm.linux.org.uk/news/?newsitem=11
> >thanks,
> >
> >greg k-h
> >
> Thanks for your response.
As you sent this to me privately, I take it you didn't read the above
link?
> Is there an official udev web page or forum?
No, nothing is ever "official" :)
The linux-hotplug-devel mailing list has been a good place to discuss
udev stuff.
> As to why not use mailing list in the first place: A. Who wants to get
> flamed by Al in public. ;-) B. Giving consideration to the developer
> who might want to discuss the issue before exposing it to a public
> forum. I probably have sent about 50 emails to the LKML over the last
> eight years on topics from VMM to SCSI to SCM, but sometimes it seems
> better to directly address the relevant developer. Not everyone
> subscribes to the list after all. ;-)
But it saves developer time, which is in much shorter supply than "users
who don't read the documentation time" it seems...
greg k-h
next prev parent reply other threads:[~2003-10-07 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F830C49.5070103@greshamstorage.com>
2003-10-07 19:05 ` Linux 2.6 udev capability question Greg KH
[not found] ` <3F831AAB.9040000@greshamstorage.com>
2003-10-07 20:24 ` Greg KH [this message]
2003-10-07 20:34 ` Acknowledgement Jonathan A. George
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=20031007202412.GF2670@kroah.com \
--to=greg@kroah.com \
--cc=JAGeorge@greshamstorage.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