From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/2] libopenssl: bump version to 1.1.1a
Date: Tue, 22 Jan 2019 22:08:52 +0100 [thread overview]
Message-ID: <877eewo0wr.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <ad65c62d-eef9-2113-cfb6-6b5941958285@mind.be> (Arnout Vandecappelle's message of "Tue, 22 Jan 2019 12:23:14 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
> At some point, we'll just have to let an autobuilder detect the issues. Some
> issues anyway only become apparent at link time, so when building a dependency
> of a dependency...
> We have an autobuilder running on an openssl-bump branch and Patrick is fixing
> the issues that come out. But at some point we'll need to just bite the bullet
> and accept the whole thing.
> I do hope that it could still go into 2019.02.
If that is our goal, then we might as well merge it ASAP to get more
test coverage?
What is the killer feature why we need openssl-1.1.x in 2019.02.x? TLS
1.3 or just that 1.0.2 goes EOL at the end of the year?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-01-22 21:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 22:42 [Buildroot] [PATCH v4 1/2] libopenssl: bump version to 1.1.1a Peter Seiderer
2019-01-15 22:42 ` [Buildroot] [PATCH v4 2/2] freeswitch: bump to git master 8f10ae54a18a19fc6ed938e4f662bd218ba54b5e Peter Seiderer
2019-01-16 1:40 ` [Buildroot] [PATCH v4 1/2] libopenssl: bump version to 1.1.1a Ryan Coe
2019-01-16 11:46 ` Arnout Vandecappelle
2019-01-16 14:27 ` Peter Seiderer
2019-01-16 5:52 ` Baruch Siach
2019-01-16 13:58 ` Vadim Kochan
2019-01-17 18:43 ` Peter Seiderer
2019-01-22 11:23 ` Arnout Vandecappelle
2019-01-22 21:08 ` Peter Korsgaard [this message]
2019-01-23 14:29 ` Arnout Vandecappelle
2019-01-23 16:15 ` Peter Korsgaard
2019-01-23 22:44 ` Arnout Vandecappelle
2019-01-23 23:03 ` Peter Korsgaard
2019-01-25 23:27 ` Arnout Vandecappelle
-- strict thread matches above, loose matches on Subject: below --
2019-01-16 11:43 Patrick Havelange
2019-01-16 14:24 ` Peter Seiderer
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=877eewo0wr.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox