From: Martin Waitz <tali@admingilde.org>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Jeff Garzik <jgarzik@pobox.com>, Mariusz Mazur <mmazur@kernel.pl>,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] linux-libc-headers 2.6.7.0
Date: Fri, 25 Jun 2004 11:25:57 +0200 [thread overview]
Message-ID: <20040625092557.GG27805@admingilde.org> (raw)
In-Reply-To: <m3n02s9a9f.fsf@defiant.pm.waw.pl>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
hi :)
On Thu, Jun 24, 2004 at 06:43:56PM +0200, Krzysztof Halasa wrote:
> > HPA suggested include/abi and I don't think anyone objected.
well, include/abi looks very generic. For userspace code, I really
like to have 'linux' in the include file name, so that it's clear that
some linux-specific header is being used.
> /usr/include/abi -> linux/include/abi
> /usr/include/linux -> abi (obsolete, to be removed with 2.8)
> Appropriate $ARCH + generic dirs (names?).
what about keeping /usr/include/linux for the userspace visible part
of the linux headers and using a new name for the internal headers.
That way we don't have to change userspace applications and can
do all modifications in the kernel tree at the time we want.
For example:
* mkdir include/kernel (plus arch-specific versions)
* add placeholer files that simply #include the old include/linux file
* start replacing in-kernel #includes with the include/kernel version.
* move the #ifdef __KERNEL__ parts from include/linux to include/kernel
This can be done incrementally, too.
--
Martin Waitz
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-25 9:26 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
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 [this message]
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=20040625092557.GG27805@admingilde.org \
--to=tali@admingilde.org \
--cc=jgarzik@pobox.com \
--cc=khc@pm.waw.pl \
--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