From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-announce@cygwin.com
Subject: [HEADSUP] Intermediate 1.7.33 release coming
Date: Thu, 13 Nov 2014 12:14:00 -0000 [thread overview]
Message-ID: <20141113120907.GA30892@calimero.vinschen.de> (raw)
Hi folks,
Given the ongoing discussion about required changes to the new, Windows
SAM/AD-based account handling in Cygwin, the release coming with these
changes will be deferred until we have a satisfying solution for this.
However, there's a good number of changes compared to 1.7.32 in the
repository which are likewise important and shouldn't be deferred any
longer.
Therefore I'm going to release an intermediate 1.7.33 release in the
next couple of hours, which comes with most, but not all changes from
the 1.7.33 test releases.
The new test release will have a 1.7.34-xxx version number, so don't
be surprised. You have been warned and all that.
Thanks for reading,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
reply other threads:[~2014-11-13 12:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20141113120907.GA30892@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-announce@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).