From: Erik Andersen <andersen@codepoet.org>
To: Mariusz Mazur <mmazur@kernel.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] linux-libc-headers 2.6.2.0
Date: Wed, 11 Feb 2004 16:28:29 -0700 [thread overview]
Message-ID: <20040211232829.GA15450@codepoet.org> (raw)
In-Reply-To: <200402112339.55593.mmazur@kernel.pl>
On Wed Feb 11, 2004 at 11:39:55PM +0100, Mariusz Mazur wrote:
> Available at: http://ep09.pld-linux.org/~mmazur/linux-libc-headers/
>
> Changes:
> - applied changes from 2.6.2 kernel
> - added an empty linux/compiler.h (I really hate myself for doing this, but
> don't have much choice... many apps include it as a workaround for broken
> headers that come with linux)
> - some minor changes... mostly removing duplicate definitons and replacing
> them with calls to glibc's headers
Thoughts on adding sanitized include/scsi/ ?
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2004-02-11 23:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 22:39 [ANNOUNCE] linux-libc-headers 2.6.2.0 Mariusz Mazur
2004-02-11 23:28 ` Erik Andersen [this message]
2004-02-11 23:40 ` Mariusz Mazur
2004-02-11 23:32 ` Erik Andersen
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=20040211232829.GA15450@codepoet.org \
--to=andersen@codepoet.org \
--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