From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev - udevd/udevsend man page
Date: Wed, 18 Feb 2004 19:07:20 +0000 [thread overview]
Message-ID: <20040218190720.GA10007@vrfy.org> (raw)
In-Reply-To: <20040217022011.GA5949@vrfy.org>
On Wed, Feb 18, 2004 at 10:04:25AM -0800, Greg KH wrote:
> On Tue, Feb 17, 2004 at 08:50:16PM +0100, Kay Sievers wrote:
> > On Tue, Feb 17, 2004 at 11:00:26AM -0800, Greg KH wrote:
> > > On Tue, Feb 17, 2004 at 03:20:11AM +0100, Kay Sievers wrote:
> > > > Here is the missing man page for udevd/udevsend.
> > >
> > > Applied, thanks.
> > >
> > > > Hey, I get a beer now, this is my 100th udev patch :)
> > >
> > > I'll be very glad to buy you one whenever we meet up :)
> >
> > Nice, maybe at OLS this year?
> > I'll see, if I can manage it to come.
>
> I'll be there.
>
I'm looking forward...
> Now I only have to come up with a paper topic...
Oh, what's about the true random device number allocation?
Not really new, but udev fits nice here :)
Or what happened to the parallel device probing thing?
Kay
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
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
next prev parent reply other threads:[~2004-02-18 19:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 2:20 [PATCH] udev - udevd/udevsend man page Kay Sievers
2004-02-17 19:00 ` Greg KH
2004-02-17 19:50 ` Kay Sievers
2004-02-18 18:04 ` Greg KH
2004-02-18 19:07 ` Kay Sievers [this message]
2004-02-18 19:20 ` 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=20040218190720.GA10007@vrfy.org \
--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.