From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] socat: security bump to version 2.0.0-b9
Date: Tue, 2 Feb 2016 12:59:20 -0300 [thread overview]
Message-ID: <56B0D258.30306@zacarias.com.ar> (raw)
In-Reply-To: <871t8v5dr9.fsf@dell.be.48ers.dk>
On 02/02/16 12:32, Peter Korsgaard wrote:
> What is this about? A new issue introduced in 2.0.0-b9? Musl fix? Your
> commit message didn't mention anything about it?
It's a general build fix.
>> # From http://www.dest-unreach.org/socat/download.md5sum
> > -md5 ff56576703dfdeac221357a348c30760 socat-2.0.0-b8.tar.bz2
> > +md5 553b1593d0a192cb09cbdc687ef1baac socat-2.0.0-b9.tar.bz2
> > +#
>
> Missing text? Locally calculated?
Sent v2 addressing this.
Regards.
prev parent reply other threads:[~2016-02-02 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 12:40 [Buildroot] [PATCH] socat: security bump to version 2.0.0-b9 Gustavo Zacarias
2016-02-02 15:32 ` Peter Korsgaard
2016-02-02 15:59 ` Gustavo Zacarias [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=56B0D258.30306@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.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