From: Christoph Hellwig <hch@infradead.org>
To: Mariusz Mazur <mmazur@kernel.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] linux-libc-headers 2.6.5.1
Date: Mon, 3 May 2004 19:47:57 +0100 [thread overview]
Message-ID: <20040503194757.A13711@infradead.org> (raw)
In-Reply-To: <200405030111.49802.mmazur@kernel.pl>; from mmazur@kernel.pl on Mon, May 03, 2004 at 01:11:49AM +0200
On Mon, May 03, 2004 at 01:11:49AM +0200, Mariusz Mazur wrote:
> Available at http://ep09.pld-linux.org/~mmazur/linux-libc-headers/
> Changes:
> - network headers got fixed - most notably removed most common collisions
> between glibc and llh (I hate making hacks, but don't have much choice -
> glibc's network headers lack functionality); iproute2 and iputils should
> build with just small patches (which can be found at the above url) and
> including linux/{in*,if*} in general should be quite safe now
Maybe someone should spend some time and fix up the glibc headers instead? :)
next prev parent reply other threads:[~2004-05-03 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-02 23:11 [ANNOUNCE] linux-libc-headers 2.6.5.1 Mariusz Mazur
2004-05-03 18:47 ` Christoph Hellwig [this message]
2004-05-03 19:24 ` Kevin P. Fleming
2004-05-03 19:31 ` Christoph Hellwig
2004-05-03 20:05 ` Mariusz Mazur
2004-05-05 1:49 ` 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=20040503194757.A13711@infradead.org \
--to=hch@infradead.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