From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Please test latest developer snapshot
Date: Thu, 24 Feb 2011 15:16:00 -0000 [thread overview]
Message-ID: <20110224151611.GA24521@calimero.vinschen.de> (raw)
In-Reply-To: <AANLkTimcEa6XvG3se-TYDEm=ujSCQ7V5d3GQUF4mNnfS@mail.gmail.com>
On Feb 24 09:56, Chris Sutcliffe wrote:
> On 17 February 2011 07:04, Corinna Vinschen wrote:
> > Apart from your testing and our fixing of obvious bugs, the other item
> > holding up the release of Cygwin 1.7.8 is the imminent release of
> > Service Pack 1 for Windows 7. Â It seems unwise to release a new Cygwin
> > package just minutes before a Service Pack comes out. Â Given the latest
> > experience that even monthly fixes can come with a nice, hidden gift, I
> > rather wait for a couple of days and test with SP1 first.
>
> Just a heads up, I've been testing the latest snapshot on Win7SP1 x64
> and have not encountered any issues as of yet in my day-to-day use.
Thank you! I'm running SP1 32 and 64 bit for a couple of days now, too.
But we all have different usage profiles so I appreciate to get this
kind of feedback.
If there's nothing else missing, I'm planning to release 1.7.8 on the
weekend or early next week.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-02-24 15:16 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 12:04 Corinna Vinschen
2011-02-17 18:06 ` Ken Brown
2011-02-17 18:15 ` marco atzeri
2011-02-18 12:36 ` Corinna Vinschen
2011-02-18 13:34 ` marco atzeri
2011-02-17 19:33 ` Aaron Peromsik
2011-02-17 20:15 ` Yaakov (Cygwin/X)
2011-02-19 18:29 ` Warren Young
2011-02-19 18:35 ` Warren Young
2011-02-19 20:35 ` Warren Young
2011-02-20 12:16 ` Corinna Vinschen
2011-02-21 14:16 ` Eric Blake
2011-02-21 15:21 ` Thomas Wolff
2011-02-26 0:25 ` Vorfeed Canal
2011-02-26 0:45 ` Eric Blake
2011-02-26 1:03 ` Thomas Wolff
2011-02-27 7:35 ` Vorfeed Canal
2011-02-27 10:21 ` Vorfeed Canal
2011-02-27 11:21 ` Vorfeed Canal
2011-02-24 14:57 ` Chris Sutcliffe
2011-02-24 15:16 ` Corinna Vinschen [this message]
2011-02-24 19:34 ` Karl M
2011-02-24 20:56 ` Reini Urban
2011-02-24 21:52 ` Kai Tietz
2011-02-25 9:47 ` Corinna Vinschen
2011-02-25 23:25 ` David Rothenberger
2011-02-26 0:09 ` David Rothenberger
2011-02-26 9:51 ` marco atzeri
2011-02-26 10:36 ` Corinna Vinschen
2011-02-27 14:15 ` Corinna Vinschen
2011-02-27 18:45 ` David Rothenberger
2011-03-01 7:06 ` Christopher Faylor
2011-03-01 15:51 ` David Rothenberger
2011-02-18 15:34 Angelo Graziosi
2011-02-19 16:05 ` jdzstz - gmail dot com
2011-02-27 15:03 Angelo Graziosi
[not found] <AANLkTim4xT_LL=CGFXhgKmO0gLd5P_rXctaMpHwT2pxn@mail.gmail.com>
2011-03-03 12:22 ` Oleg Marchuk
2011-03-03 12:53 ` Oleg Marchuk
2011-03-03 16:41 ` Christopher Faylor
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=20110224151611.GA24521@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.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).