From: Andrea Arcangeli <andrea@suse.de>
To: linux-kernel@vger.kernel.org
Subject: 2.2.20pre9aa2
Date: Sat, 18 Aug 2001 06:06:31 +0200 [thread overview]
Message-ID: <20010818060631.B1719@athlon.random> (raw)
Diff between 2.2.20pre9aa1 and 2.2.20pre9aa2:
Only in 2.2.20pre9aa1: 00_poll-nfds-1
Only in 2.2.20pre9aa2: 00_poll-nfds-2
Fixed off by one error in the rlimit check.
Only in 2.2.20pre9aa1: 40_lfs-2.2.19pre16aa1-26.bz2
Only in 2.2.20pre9aa2: 40_lfs-2.2.20pre9aa2-27.bz2
Drop obsolete (and duplicated) fcntl64 definition in the sparc
unistd.h. (this was a lonstanding bug, it never triggered yet because
glibc gets compiled with the 2.4 headers)
Andrea
reply other threads:[~2001-08-18 4:06 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=20010818060631.B1719@athlon.random \
--to=andrea@suse.de \
--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