From: Robert Klemme <shortcutter@googlemail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>, cygwin-announce@cygwin.com
Subject: Re: Updated: bash-4.1.14-7
Date: Tue, 30 Sep 2014 07:36:00 -0000 [thread overview]
Message-ID: <CAM9pMnPgXLf1sB=7mKmJ-9UC2i6E-JFQo4y5gwfMt9JDVaawTw@mail.gmail.com> (raw)
In-Reply-To: <5429CDA3.8080300@byu.net>
On Mon, Sep 29, 2014 at 11:22 PM, Eric Blake (cygwin) wrote:
> A new release of bash, 4.1.14-7, has been uploaded and will soon reach a
> mirror near you; leaving the previous version at 4.1.13-6.
...
Thank you Eric for the fast updates and staying on top of all the
security warnings coming in!
Kind regards
robert
--
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
parent reply other threads:[~2014-09-30 7:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5429CDA3.8080300@byu.net>]
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='CAM9pMnPgXLf1sB=7mKmJ-9UC2i6E-JFQo4y5gwfMt9JDVaawTw@mail.gmail.com' \
--to=shortcutter@googlemail.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).