Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] socat version
Date: Sat, 08 Nov 2014 22:22:02 +0100	[thread overview]
Message-ID: <874mu9tmkl.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CANxTyt5UVteo4xOJ85YfZP4J-3ZpVstGjnr8Yj4Sry93zfUqzg@mail.gmail.com> (Danomi Manchego's message of "Tue, 4 Nov 2014 07:58:35 -0500")

>>>>> "Danomi" == Danomi Manchego <danomimanchego123@gmail.com> writes:

 > All,
 > Buildroot has been using the socat 2.0.0 series for a while.  We
 > recently ran into a socat issue which was fixed upstream, but in a
 > 1.7.2.4 release.  For rears, the socat people released a version 1
 > release and a version 2 release in tandem, but for some reason, the
 > latest release was only 1.7.2.4.  Reading about socat 2 at
 > http://www.dest-unreach.org/socat/socat-version2.html I see it is
 > (was?) described as "beta".

 > So I was wondering: is buildroot on the 2.0.0 series under the
 > normally sane presumption that 2.0 must be newer than 1.7, or is there
 > an actual preference for the version 2 releases?

I don't think there's any real reason that we've gone with 2.0 series. I
atleast wasn't aware of the two branches. We moved from 1.4 to 2.0 a
long time ago (back when we used subversion), and the person doing the
change is no longer active.

commit 3fde5702db832475c4a45aa3f35aac7839c6a710
Author: Ulf Samuelsson <ulf.samuelsson@atmel.com>
Date:   Fri Jan 2 08:29:31 2009 +0000

    Bump socat version, optionally add configure variables

Gustavo, you have recently bumped the version - Do you have anything to
add?

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2014-11-08 21:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 12:58 [Buildroot] socat version Danomi Manchego
2014-11-04 13:13 ` Yegor Yefremov
     [not found]   ` <54591B92.4030502@dest-unreach.org>
2014-11-09 12:33     ` Yegor Yefremov
2014-11-08 21:22 ` Peter Korsgaard [this message]
2014-11-09 11:17   ` Gustavo Zacarias

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=874mu9tmkl.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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