From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 016 release
Date: Wed, 04 Feb 2004 22:31:59 +0000 [thread overview]
Message-ID: <20040204223159.GG3897@kroah.com> (raw)
In-Reply-To: <20040203201359.GB19476@kroah.com>
On Tue, Feb 03, 2004 at 10:30:01PM +0100, Marco d'Itri wrote:
> On Feb 03, Greg KH <greg@kroah.com> wrote:
>
> I'm attaching a trivial patch to remove a warning.
Thanks, Kay already sent me that.
> BTW, udev still takes a long time to start when D-BUS support is
> enabled.
That's a D-BUS issue, not a udev issue :)
thanks,
greg k-h
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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-04 22:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 20:13 [ANNOUNCE] udev 016 release Greg KH
2004-02-03 21:30 ` Marco d'Itri
2004-02-03 22:23 ` Eric Sandall
2004-02-03 22:46 ` Greg KH
[not found] ` <1075843712.7473.60.camel@nosferatu.lan>
[not found] ` <1075849413.11322.6.camel@nosferatu.lan>
2004-02-03 23:13 ` Greg KH
2004-02-04 0:01 ` Kay Sievers
[not found] ` <1075841390.7473.57.camel@nosferatu.lan>
2004-02-03 23:14 ` Greg KH
2004-02-03 23:33 ` Eric Sandall
2004-02-03 23:53 ` Greg KH
2004-02-04 0:35 ` Eric Sandall
2004-02-04 22:31 ` Greg KH [this message]
[not found] ` <1075844602.7473.75.camel@nosferatu.lan>
2004-02-11 22:13 ` Greg KH
[not found] ` <1076538429.22542.12.camel@nosferatu.lan>
2004-02-12 1:19 ` 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=20040204223159.GG3897@kroah.com \
--to=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).