From: Ross Johnson <rpj@ise.canberra.edu.au>
To: "Pthreads-Win32@Sources.Redhat.Com" <pthreads-win32@sources.redhat.com>
Subject: CVS repository
Date: Thu, 13 Dec 2001 22:28:00 -0000 [thread overview]
Message-ID: <3C199BF7.D7605D27@ise.canberra.edu.au> (raw)
Message-ID: <20011213222800.vrLvdrkmF-fwQlI47DKgkIaKBagotTIr2-twLhkshX4@z> (raw)
In-Reply-To: <3C197E49.E41DCCE@ise.canberra.edu.au>
This is probably a good time to mention that, since
the last snapshot there have been some updates to the
source code in the CVS repository.
I'm mentioning this because it's been quite a while
since the last snapshot release, and the next one
probably won't be out before the new year, possibly
not until february.
A couple of people have recently sent me changes and
bug fixes, some of which have been done already
(in CVS), and the rest will appear in CVS of course
a lot sooner than the next snapshot. Generally I try
to make sure any new changes pass the test suite
before committing them to CVS.
There's information at
http://source.redhat.com/pthreads-win32
re getting and using CVS (or WinCVS) if you don't
use it already.
Cheers.
Ross
next prev parent reply other threads:[~2001-12-13 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-01 23:21 What's the suggested way to build pthreads? Magnus Zakrisson
2001-01-01 23:27 ` Phil Frisbie, Jr.
2001-12-13 7:30 ` Phil Frisbie, Jr.
2001-01-02 10:24 ` Ross Johnson
2001-01-02 16:31 ` Ross Johnson [this message]
2001-12-13 22:28 ` CVS repository Ross Johnson
2001-12-13 20:21 ` What's the suggested way to build pthreads? Ross Johnson
2001-12-13 2:37 ` Magnus Zakrisson
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=3C199BF7.D7605D27@ise.canberra.edu.au \
--to=rpj@ise.canberra.edu.au \
--cc=pthreads-win32@sources.redhat.com \
/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).