From: Rob Landley <rob@landley.net>
To: Nix <nix@esperi.org.uk>
Cc: Blaisorblade <blaisorblade@yahoo.it>,
user-mode-linux-devel@lists.sourceforge.net, mmazur@kernel.pl
Subject: Re: [uml-devel] Re: merge status
Date: Mon, 21 Nov 2005 08:51:20 -0600 [thread overview]
Message-ID: <200511210851.20951.rob@landley.net> (raw)
In-Reply-To: <87hda65mbv.fsf@amaterasu.srvr.nix>
On Monday 21 November 2005 04:25, Nix wrote:
> On Fri, 18 Nov 2005, Rob Landley wrote:
> > On Friday 18 November 2005 20:33, Blaisorblade wrote:
> >> Btw, why hasn't maszur went to post patches to kernel headers to make
> >> them includable from userspace instead of merging kernel changes into
> >> his headers (which is much more work)?
> >
> > For the same reason the glibc guys don't ship a patch against the kernel
> > headers but ship cleaned upkernel headers. It's much smaller and
> > simpler, and the patch would break with every single release. Besides,
> > the patch isn't what we need to build libc, the cleaned up headers are.
> > It would add an unnecessary level of indirection and _never_ get merged
> > into the main kernel?
>
> One problem is that Mariusz's linux-libc-headers work seems to have
> stalled :( the last headers out there are for 2.6.12, and increasingly much
> (e.g. iptables) needs to be pointed directly at the kernel headers again.
>
> I hope linux-libc-headers isn't dead. It looked like it was turning into
> a very good aggregation point, with patches coming in from Ubuntu and RH
> among others.
Hopefully he won't mind me quoting from his email on Nov 4th. Project's not
dead, he's just busy with Real Life (tm):
> I'm also CCing Wojtek Cieciwa (cieciwa@pld-linux.org), since he's one of the
> guys that need a new llh release and I should be releasing 2.6.14.0 right
> about now (my world kind of collapsed a few days ago and I'm out of the
> picture for don't know how long; I hope to be able to recover within a week,
> but who nows how things will work out; keep me CCed though).
Rob
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-11-21 14:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051109133558.513facef.akpm@osdl.org>
[not found] ` <20051109150141.0bcbf9e3.akpm@osdl.org>
[not found] ` <Pine.LNX.4.64.0511091547160.4627@g5.osdl.org>
2005-11-16 13:36 ` [uml-devel] Re: merge status Rob Landley
2005-11-18 7:08 ` Blaisorblade
2005-11-18 7:17 ` Rob Landley
2005-11-18 7:51 ` Blaisorblade
2005-11-18 8:41 ` Rob Landley
2005-11-19 2:33 ` Blaisorblade
2005-11-19 3:26 ` Rob Landley
[not found] ` <87hda65mbv.fsf@amaterasu.srvr.nix>
2005-11-21 14:51 ` Rob Landley [this message]
2005-11-21 19:41 ` Nix
2005-11-19 23:40 ` Henrik Nordstrom
2005-11-20 16:32 ` Blaisorblade
2005-11-18 23:52 ` Jeff Dike
2005-11-18 23:37 ` Rob Landley
2005-11-19 0:55 ` Jeff Dike
2005-11-19 0:06 ` Rob Landley
2005-11-30 17:23 ` Michael Richardson
2005-12-02 0:15 ` Blaisorblade
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=200511210851.20951.rob@landley.net \
--to=rob@landley.net \
--cc=blaisorblade@yahoo.it \
--cc=mmazur@kernel.pl \
--cc=nix@esperi.org.uk \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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