From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] socat: bump down to version 1.7.3.2
Date: Sun, 29 Oct 2017 18:15:44 +0100 [thread overview]
Message-ID: <20171029181544.679a0e1c@windsurf> (raw)
In-Reply-To: <d6ae63148fa0ada0848cb05f2d6b5d6fde70114f.1509287629.git.baruch@tkos.co.il>
Hello,
On Sun, 29 Oct 2017 16:33:49 +0200, Baruch Siach wrote:
> Upstream socat2 branch seems to be dead. Last commit is from January
> 2016 . Over the last few years socat2 received only fixes cherry picked
> from the master 1.x branch. Most major general purpose distros only
> package socat 1.x.
>
> Drop the threads dependency; not needed for 1.x.
>
> Mention the OpenSSL exception in the license. Add hashes for license
> files.
>
> Correct the autoconf comment. The tarball configure script is recent
> enough. But since we patch configure.in and Makefile.in we still need to
> autoconf.
>
> All patches we carry for socat2 are also needed for socat 1.x.
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/socat/Config.in | 5 -----
> package/socat/socat.hash | 8 ++++++--
> package/socat/socat.mk | 13 ++++++-------
> 3 files changed, 12 insertions(+), 14 deletions(-)
Applied to master, thanks. Are you using socat? If so, could you list
yourself in the DEVELOPERS file for this package?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-10-29 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 14:33 [Buildroot] [PATCH] socat: bump down to version 1.7.3.2 Baruch Siach
2017-10-29 17:15 ` Thomas Petazzoni [this message]
2017-10-30 5:04 ` Baruch Siach
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=20171029181544.679a0e1c@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--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 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.