From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Reporting Message
Date: Thu, 02 Dec 2004 21:10:31 +0000 [thread overview]
Message-ID: <1102021831.6127.20.camel@localhost.localdomain> (raw)
In-Reply-To: <E1CZnb9-0005Ad-AC@sc8-sf-mx1.sourceforge.net>
On Thu, 2004-12-02 at 10:37 -0800, Greg KH wrote:
> On Thu, Dec 02, 2004 at 07:45:50AM -0800, Paul Jackson wrote:
> > Next time someone needs to collect data like this,
> > instead of having the message request a post to an
> > email list, perhaps it should point to a web page.
> >
> > Initially, the web page would then ask for the email
> > posting. But then it could be changed - to explain
> > that it no longer mattered.
>
> Well, we never counted on a distro actually leaving those messages in :)
>
> Almost all of the reports here are because of Fedora Core 3 picking up
> wait_for_sysfs a bit early in it's development process.
Yeah, but the good point is that it annoyed me so much. :) It was the
incentive to export what to wait for (PHYSDEVPATH, PHYSDEVBUS) from the
kernel (2.6.10), which seems to work well.
> Oh well, we learn and move on :)
Yes, a link to a web page is a good idea. We may try that next time.
Thanks,
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-12-02 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 9:51 Reporting Message Darren Keech
2004-12-02 10:25 ` Kay Sievers
2004-12-02 15:45 ` Paul Jackson
2004-12-02 18:37 ` Greg KH
2004-12-02 20:51 ` Paul Jackson
2004-12-02 21:10 ` Kay Sievers [this message]
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=1102021831.6127.20.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.