From: Ross Johnson <rpj AT ise.canberra.edu.au>
To: Pthreads Developers List <pthreads-win32 AT sourceware.cygnus.com>
Subject: What will be in the next snapshot, due soon.
Date: Mon, 13 Sep 1999 23:00:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.05.9909141517040.20967-100000@swan.canberra.edu.au> (raw)
Hi all,
Just to let people know what to expect in the next snapshot, which I
will get out just as soon as I write a few more tests for Aurelio
Medina's rwlock code. The three simple tests written so far have
all passed.
Apart from contributed bug fixes, there is Aurelio's rwlock
routines. I've modified Aurelio's code slightly to conform to the
style used for other opaque objects in the library (mutexes and
cond vars etc).
Mumit Khan's patches to enable building the library under
Mingw32/MSVCRT are in there too.
Ross
+----------------------+---+
| Ross Johnson | | E-Mail: rpj@ise.canberra.edu.au
| Info Sciences and Eng|___|
| University of Canberra | FAX: +61 6 2015227
| PO Box 1 |
| Belconnen ACT 2616 | WWW: http://willow.canberra.edu.au/~rpj/
| AUSTRALIA |
+--------------------------+
next reply other threads:[~1999-09-13 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-13 23:00 Ross Johnson [this message]
1999-09-14 20:34 ` Mumit Khan
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=Pine.LNX.4.05.9909141517040.20967-100000@swan.canberra.edu.au \
--to=pthreads-win32@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).