From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Mariusz Mazur <mmazur@kernel.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] linux-libc-headers 2.6.7.0
Date: Wed, 23 Jun 2004 19:48:56 -0400 [thread overview]
Message-ID: <40DA16E8.6070902@nortelnetworks.com> (raw)
In-Reply-To: <200406240102.23162.mmazur@kernel.pl>
Mariusz Mazur wrote:
> I'm interested in guidelines, not discussion :)
> Kernel guys had a couple of years since 2.4 for discussing this so
> something
> *must* have been agreed upon.
After a bit of googling...
Andries Brouwer suggested include/linuxabi with arch-specific dirs
H. Peter Anvin apparently suggested putting them in include/abi, with
arch-specific dirs. However, he thinks its too much work for 2.6 and sees it as
an early 2.7 thing.
Matthew Wilcox apparently suggested something similar
Jeff Garzik approved the idea
Rob Landley suggested moving your headers there and then cleaning up the other
headers, and expressed willingness to submit patches.
Sam Ravnborg supported the idea
Eric Biederman supported the idea, suggested linux-only namespace and
version-based naming, figured it was 2.7 work
David Miller approved the idea
Maybe this should be a topic for the kernel summit or a BOF session at OLS?
Chris
next prev parent reply other threads:[~2004-06-23 23:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 22:20 [ANNOUNCE] linux-libc-headers 2.6.7.0 Mariusz Mazur
2004-06-23 22:54 ` Chris Friesen
2004-06-23 23:02 ` Mariusz Mazur
2004-06-23 23:48 ` Chris Friesen [this message]
2004-06-24 5:58 ` Greg KH
2004-06-24 9:18 ` Jeff Garzik
2004-06-24 11:02 ` Mariusz Mazur
2004-06-24 13:53 ` Andries Brouwer
2004-06-24 19:29 ` Sam Ravnborg
2004-06-23 23:17 ` Jeff Garzik
2004-06-23 23:30 ` Mariusz Mazur
2004-06-24 16:43 ` Krzysztof Halasa
2004-06-25 9:25 ` Martin Waitz
2004-06-25 10:02 ` Andries Brouwer
2004-06-25 11:33 ` Rob Landley
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=40DA16E8.6070902@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmazur@kernel.pl \
/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