From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Cc: Jari Aalto <jari.aalto@cante.net>
Subject: Re: Mercurial update needed for security fixes
Date: Mon, 18 Sep 2017 16:58:00 -0000 [thread overview]
Message-ID: <6af6ce98-5a26-675b-3ac7-e7fb7540274e@cornell.edu> (raw)
In-Reply-To: <vz1wp4wc9i6.fsf@gmail.com>
On 9/18/2017 11:27 AM, Andy Moreton wrote:
> On Thu 17 Aug 2017, Andy Moreton wrote:
>
> Ping?
>
>> Hi,
>>
>> Can the mercurial maintainer please update to upstream Hg 4.3.1, to get
>> the fixes for CVE-2017-1000115 and CVE-2017-1000116.
I don't know if he reads the list. I'm adding him to the Cc.
Ken
--
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:[~2017-09-18 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 9:49 Andy Moreton
2017-09-18 15:27 ` Andy Moreton
2017-09-18 16:58 ` Ken Brown [this message]
2017-09-25 17:31 ` Andy Moreton
2017-09-25 17:35 ` Vince Rice
2017-09-26 13:24 ` Mercurial update needed for security fixes (fixed in 4.3.2-1) Jari Aalto
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=6af6ce98-5a26-675b-3ac7-e7fb7540274e@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
--cc=jari.aalto@cante.net \
/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).