From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: libgcrypt: Update to 1.6.5. (security update)
Date: Thu, 11 Feb 2016 10:52:07 +0100 [thread overview]
Message-ID: <8737szvak8.fsf@gnu.org> (raw)
In-Reply-To: <20160210205654.GA20730@debian> (Andreas Enge's message of "Wed, 10 Feb 2016 21:56:54 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> On Wed, Feb 10, 2016 at 03:46:03PM -0500, Mark H Weaver wrote:
>> What's the nature of the pulseaudio update? Why is it important?
>
> It is not particularly important, I would say. I am just growing impatient,
Of course having Hydra stuck building security updates is a bit
frustrating when we’d all want to have fun with the cutting edge stuff…
but I think it’s important nonetheless. So I’m all for having the
Graphite fix take precedence over the rest.
But really, we should fix <http://bugs.gnu.org/22139>. That would give
us some breathing room.
Ludo’.
prev parent reply other threads:[~2016-02-11 9:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 19:52 [PATCH] gnu: libgcrypt: Update to 1.6.5. (security update) Christopher Allan Webber
2016-02-09 20:15 ` Mark H Weaver
2016-02-09 20:31 ` Christopher Allan Webber
2016-02-10 14:46 ` Andreas Enge
2016-02-10 16:53 ` wip-pulseaudio (was Re: [PATCH] gnu: libgcrypt: Update to 1.6.5. (security update)) Efraim Flashner
2016-02-10 18:41 ` Efraim Flashner
2016-02-10 18:55 ` Andreas Enge
2016-02-10 20:43 ` Andreas Enge
2016-02-10 20:46 ` [PATCH] gnu: libgcrypt: Update to 1.6.5. (security update) Mark H Weaver
2016-02-10 20:56 ` Andreas Enge
2016-02-11 9:52 ` Ludovic Courtès [this message]
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=8737szvak8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.