From: ng0 <ng0@infotropique.org>
To: Leo Famulari <leo@famulari.name>
Cc: 28027@debbugs.gnu.org
Subject: [bug#28027] curl security update [was Re: bug#28027: gnURL 7.55.0]
Date: Wed, 9 Aug 2017 19:54:15 +0000 [thread overview]
Message-ID: <20170809195415.zfrn3m4su53vdsb7@abyayala> (raw)
In-Reply-To: <20170809185007.GA1177@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
Leo Famulari transcribed 1.6K bytes:
> On Wed, Aug 09, 2017 at 01:48:42PM -0400, Leo Famulari wrote:
> > On Wed, Aug 09, 2017 at 06:25:39PM +0200, Tobias Geerinckx-Rice wrote:
> > > ng0 wrote on 09/08/17 at 18:00:
> > > > From 13129d51ac4dd5ac7f5e7b74997297139a40be12 Mon Sep 17 00:00:00 2001
> > > > From: ng0 <ng0@infotropique.org>
> > > > Date: Wed, 9 Aug 2017 15:58:43 +0000
> > > > Subject: [PATCH] gnu: gnurl: Update to 7.55.0.
> > > >
> > > > * gnu/packages/gnunet.scm (gnurl): Update to 7.55.0.
> > >
> > > Thanks! Pushed as 28e12d6c81cef2aca7f792f3c99037a649faa9b0.
> >
> > Great! Can somebody also update the curl replacement?
>
> Actually, I'll do it :)
Heh. Bam, faster than cURL this time :)
Should I just do cURL and gnURL? I see changes in cURL when I make new
releases for gnURL, but I'm not volunteering for doing both ;)
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-08-09 19:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 16:00 [bug#28027] gnURL 7.55.0 ng0
2017-08-09 16:25 ` bug#28027: " Tobias Geerinckx-Rice
2017-08-09 17:48 ` [bug#28027] curl security update [was Re: bug#28027: gnURL 7.55.0] Leo Famulari
2017-08-09 18:50 ` Leo Famulari
2017-08-09 19:20 ` Leo Famulari
2017-08-09 20:05 ` ng0
2017-08-09 20:22 ` Marius Bakke
2017-08-09 21:55 ` Marius Bakke
2017-08-09 19:54 ` ng0 [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=20170809195415.zfrn3m4su53vdsb7@abyayala \
--to=ng0@infotropique.org \
--cc=28027@debbugs.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 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.