From: Benjamin LaHaise <bcrl@redhat.com>
To: linux-aio@kvack.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: libaio 0.3.90 -- test release for sync up
Date: Thu, 5 Sep 2002 01:17:55 -0400 [thread overview]
Message-ID: <20020905011755.A7979@redhat.com> (raw)
Hello,
Well, Andrea seems to be trying to fork libaio, but he never sent
any patches to me, so I don't know what his complaint with me as
maintainer is. I hope he finds it in his heart to submit *patches*
for any changes he's making. Anyways, here's a test release going
in the direction I've meant to for libaio-0.4.0 -- 0.3.15 is a
compatible release for folks running Red Hat Advanced Server and
does not break source/binary compatibility. 0.4.0 on the other
hand breaks source compatibility to match the changes made for 2.5,
but should still provide backwards compatible symbols. I've also
tossed the beginnings of man pages in man/ for people to hack on
(Alan, Bert you guys need to synch up with each other on list).
ChangeLog bits are below, the test cases have not been updated for
the new API, nor has it been tested in any way mean or form. I'll
try to get a 0.3.91 out before I leave tomorrow afternoon, but if
not it will wait until Tuesday.
-ben
--
"You will be reincarnated as a toad; and you will be much happier."
0.4.0
- remove libredhat-kernel
- add rough outline for man pages
- make the compiled io_getevents() add the extra parameter and
pass the timeout for updating as per 2.5
0.3.15
- use real syscall interface, but don't break source compatibility
yet (that will happen with 0.4.0)
next reply other threads:[~2002-09-05 5:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 5:17 Benjamin LaHaise [this message]
2002-09-05 19:42 ` libaio 0.3.90 -- test release for sync up Shailabh Nagar
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=20020905011755.A7979@redhat.com \
--to=bcrl@redhat.com \
--cc=linux-aio@kvack.org \
--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