From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/1] gnu: harfbuzz: Update to 1.0.6 [fixes CVE-2016-2052].
Date: Fri, 29 Jan 2016 03:02:27 -0500 [thread overview]
Message-ID: <87r3h0yfsc.fsf@netris.org> (raw)
In-Reply-To: <4233b75ee97a1a6d0d54c9fc54ee758a28031268.1454047197.git.leo@famulari.name> (Leo Famulari's message of "Fri, 29 Jan 2016 01:01:20 -0500")
Leo Famulari <leo@famulari.name> writes:
> * gnu/packages/gtk.scm (harfbuzz): Update to 1.0.6.
I pushed this to the 'security-updates' branch.
Thanks!
Mark
next prev parent reply other threads:[~2016-01-29 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 6:01 [PATCH 0/1] Update harfbuzz to 1.0.6 (CVE-2016-2052) Leo Famulari
2016-01-29 6:01 ` [PATCH 1/1] gnu: harfbuzz: Update to 1.0.6 [fixes CVE-2016-2052] Leo Famulari
2016-01-29 8:02 ` Mark H Weaver [this message]
2016-01-29 7:41 ` [PATCH 0/1] Update harfbuzz to 1.0.6 (CVE-2016-2052) Efraim Flashner
2016-01-29 8:04 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r3h0yfsc.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).