public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Ross Johnson <Ross.Johnson@homemail.com.au>
To: pthreads-win32@sourceware.org
Subject: Re: 2.9.0 release / win64 stability?
Date: Tue, 24 Mar 2009 23:10:00 -0000	[thread overview]
Message-ID: <49C96871.6070004@homemail.com.au> (raw)
In-Reply-To: <49C8988C.60106@emmenlauer.de>

Hi,

There's no experimental code in the current CVS head, just some bug 
fixes. Apart from a moment of weakness where I committed a patch without 
testing (recently fixed), I generally don't  commit untested changes. 
So, if it builds for you and passes all the tests, what comes out of CVS 
head at the moment should be stable.

Of course, these could be "famous last words".

And yes, in relation to 2.9.0, I should just do it. I'm still looking at 
the recent join issue but spare time is in short supply just now.

Ross

Mario Emmenlauer wrote:
>
> Hi Developers,
>
> thanks for the great project, it works fine for me (getting the
> HDF5 library threadsafe on all platforms).
>
> One question though, I could only make use of win64 using the
> latest CVS snapshot, not the 2.8.0 release. I don't feel to good
> about using a random snapshot, so I wanted to ask if there is a
> roadmap for the 2.9.0 release?
>
>
> On a side-note, the 2.8.0 release is quite dated now, and win64
> becomes increasingly important, maybe now is a good time for a
> new release? :-D Just an idea, (selfish, I admit)...
>
>
> All the best, and keep up the good work,
>
>    Mario
>

      reply	other threads:[~2009-03-24 23:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24  8:24 Mario Emmenlauer
2009-03-24 23:10 ` Ross Johnson [this message]

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=49C96871.6070004@homemail.com.au \
    --to=ross.johnson@homemail.com.au \
    --cc=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).