From: Rob Landley <rob@landley.net>
To: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Cc: Jeff Garzik <jgarzik@pobox.com>
Subject: Re: headers
Date: Tue, 19 Aug 2003 08:55:06 -0400 [thread overview]
Message-ID: <200308190855.07181.rob@landley.net> (raw)
In-Reply-To: <bhrvfh$394$1@cesium.transmeta.com>
On Monday 18 August 2003 21:45, H. Peter Anvin wrote:
> Followup to: <UTC200308181907.h7IJ7im12407.aeb@smtp.cwi.nl>
> By author: Andries.Brouwer@cwi.nl
> In newsgroup: linux.dev.kernel
>
> > From garzik@gtf.org Mon Aug 18 20:14:47 2003
> >
> > I support include/abi, or some other directory that segregates
> > user<->kernel shared headers away from kernel-private headers.
> >
> > I don't see how that would be auto-generated, though. Only created
> > through lots of hard work :)
> >
> > Yes, unfortunately. I started doing some of this a few times,
> > but it is an order of magnitude more work than one thinks at first.
> > Already the number of include files is very large.
> > And the fact that it is not just include/abi but involves the
> > architecture doesn't make life simpler.
> >
> > No doubt we must first discuss a little bit, but not too much,
> > the desired directory structure and naming.
> > Then we must do 5% of the work, and come back to these issues.
> >
> > In case people actually want to do this, I can coordinate.
> >
> > In case people want to try just one file, do signal.h.
>
> Oh yes, this is a whole lot of work.
But is it 2.6 work, or 2.8 work?
Rob
next prev parent reply other threads:[~2003-08-19 15:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 19:07 headers Andries.Brouwer
2003-08-18 21:57 ` headers Randy.Dunlap
2003-08-18 22:04 ` headers Jeff Garzik
2003-08-18 22:17 ` headers Andries Brouwer
2003-08-19 1:45 ` headers H. Peter Anvin
2003-08-19 12:55 ` Rob Landley [this message]
2003-08-19 15:45 ` headers Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2005-12-30 22:06 headers Benny Pedersen
2005-12-31 3:26 ` headers Mads Martin Joergensen
2006-01-01 20:25 ` headers Morten K. Poulsen
2006-01-02 7:30 ` headers Mads Martin Joergensen
2006-01-02 8:12 ` headers Christian Laursen
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=200308190855.07181.rob@landley.net \
--to=rob@landley.net \
--cc=hpa@zytor.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.