From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Fix cve-check (for recipe sysroots)
Date: Fri, 10 Feb 2017 15:11:17 +0200 [thread overview]
Message-ID: <918ca090-d418-e739-9d1e-35744783ce26@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LajMHhcvkD5w3R14ZdbG1JUmop-tVoehyw8+KrBL1z8Rw@mail.gmail.com>
On 02/10/2017 03:04 PM, Burton, Ross wrote:
> Abandoned may be a strong word, but I'm not sure how much development is
> being done. I do plan on looking at this and dedicating some actual
> engineering time towards it soon.
https://github.com/ikeydoherty/cve-check-tool/commits/master
Last commit on Sep 1 2016.
https://github.com/ikeydoherty/cve-check-tool/commits/rewrite-snapshot
Last commit on Aug 8 2016.
Same story with open issues and pull requests: no activity in months.
Alex
prev parent reply other threads:[~2017-02-10 13:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 19:38 [PATCH 0/3] Fix cve-check (for recipe sysroots) Jussi Kukkonen
2017-02-09 19:38 ` [PATCH 1/3] cve-check.bbclass: Fix dependencies Jussi Kukkonen
2017-02-09 19:38 ` [PATCH 2/3] cve-check-tool: Fixes for recipe sysroots Jussi Kukkonen
2017-02-09 19:38 ` [PATCH 3/3] cve-check-tool: Use CA cert bundle in correct sysroot Jussi Kukkonen
2017-11-21 8:04 ` native CA cert bundles (was: Re: [PATCH 3/3] cve-check-tool: Use CA cert bundle in correct sysroot) Patrick Ohly
2017-11-21 12:06 ` Otavio Salvador
2017-11-21 12:21 ` Patrick Ohly
2017-11-21 12:52 ` Otavio Salvador
2017-02-09 19:59 ` ✗ patchtest: failure for Fix cve-check (for recipe sysroots) Patchwork
2017-02-09 21:41 ` Leonardo Sandoval
2017-02-10 11:55 ` [PATCH 0/3] " Alexander Kanavin
2017-02-10 13:04 ` Burton, Ross
2017-02-10 13:11 ` Alexander Kanavin [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=918ca090-d418-e739-9d1e-35744783ce26@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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