From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] dump latest klibc into the udev build tree
Date: Tue, 16 Dec 2003 18:36:16 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107159988830825@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107156299722581@msgid-missing>
On Tue, Dec 16, Greg KH wrote:
> But the udev build does not contain any of those "addons" in it's
> version of the klibc tree, right? So why would it matter to udev?
Thats the reason why the subject line reads: dump the latest and greatest ...
like that:
rm -rf klibc/* ; cp -a klibc-0.94/* klibc
make KLIBC=true -j || echo patch missing
I build udev and klibc stuff in one go.
--
USB is for mice, FireWire is for men!
sUse lINUX ag, n√úRNBERG
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&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:[~2003-12-16 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 8:22 [PATCH] dump latest klibc into the udev build tree Olaf Hering
2003-12-16 8:34 ` Greg KH
2003-12-16 15:28 ` Greg KH
2003-12-16 16:33 ` Olaf Hering
2003-12-16 16:58 ` Greg KH
2003-12-16 18:36 ` Olaf Hering [this message]
2003-12-16 23:46 ` 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=marc-linux-hotplug-107159988830825@msgid-missing \
--to=olh@suse.de \
--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).