From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [V2 1/1] ntp: security bump to verserion 4.2.8p9
Date: Mon, 6 Feb 2017 16:02:32 +0100 [thread overview]
Message-ID: <20170206160232.7513524b@free-electrons.com> (raw)
In-Reply-To: <1486393216.2005.19.camel@codeblue.com>
Hello,
On Mon, 6 Feb 2017 15:00:16 +0000, Adam Duskett wrote:
> That's the million dollar question! As far as I can tell, it's a
> real decision from upstream, as many of the files now include
> libssl_compat.h, however if you want, I can try to play around
> with them and see if they are 100% mandatory or not.
That would be useful, yes.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-06 15:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 14:12 [Buildroot] [V2 1/1] ntp: security bump to verserion 4.2.8p9 Adam Duskett
2017-02-06 14:58 ` Thomas Petazzoni
[not found] ` <1486393216.2005.19.camel@codeblue.com>
2017-02-06 15:02 ` Thomas Petazzoni [this message]
2017-02-06 15:23 ` Arnout Vandecappelle
2017-02-06 21:18 ` Adam Duskett
2017-02-07 14:28 ` Peter Korsgaard
2017-02-07 14:29 ` Peter Korsgaard
2017-11-07 17:26 ` Thomas Petazzoni
2017-11-07 21:15 ` Adam Duskett
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=20170206160232.7513524b@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox