From: Mariusz Mazur <mmazur@kernel.pl>
To: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] linux-libc-headers 2.6.5.2
Date: Sun, 23 May 2004 21:37:27 +0200 [thread overview]
Message-ID: <200405232137.27555.mmazur@kernel.pl> (raw)
Available at http://ep09.pld-linux.org/~mmazur/linux-libc-headers/
Changes:
- a couple more macros for big endian machines in byteorder/swab.h (eg. hdparm
on big endian machines should build)
- missing include in linux/aio_abi.h added (don't remember what didn't build
because of this)
- removed a conflict between linux/if.h and glibc headers
I should be releasing 2.6.6.0 now, but I do not have enough time till the end
of May, and the last bug in the above list proved to be a little too popular
(at least that's what the number of bug reports would suggest). Since I've
accidentally introduced it myself in the previous release, I can't force all
those people to patch the thing by hand because of my mistakes :)
--
In the year eighty five ten
God is gonna shake his mighty head
He'll either say,
"I'm pleased where man has been"
Or tear it down, and start again
reply other threads:[~2004-05-23 19:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200405232137.27555.mmazur@kernel.pl \
--to=mmazur@kernel.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox