From: "Andrew Jeffery" <andrew@aj.id.au>
To: openbmc@lists.ozlabs.org,
"Brad Bishop" <bradleyb@fuzziesquirrel.com>,
"Gunnar Mills" <gmills@linux.vnet.ibm.com>
Subject: Re: Repository for CVE-2019-6260 test tool
Date: Wed, 20 Feb 2019 22:56:24 -0500 [thread overview]
Message-ID: <16fc4075-fd43-4d3a-b0be-1e2239e8085e@www.fastmail.com> (raw)
In-Reply-To: <24741baf-40ba-31c9-98e4-f229c4df7323@linux.vnet.ibm.com>
On Thu, 21 Feb 2019, at 14:10, Gunnar Mills wrote:
> On 2/20/2019 8:42 PM, Andrew Jeffery wrote:
>
> Can you please create a cve-2019-6260 repository under the OpenBMC
> github organisation to host the tool?
> >
> Why a new cve-2019-6260 repo instead of openbmc-tools?
No really good reason, just felt it was well defined enough to not get lumped
in with everything else in the openbmc-tools repo. openbmc-tools was
intended as a home for ill-defined scripts and bits that people had lying
around that they wouldn't have otherwise published.
Andrew
next prev parent reply other threads:[~2019-02-21 3:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 2:42 Repository for CVE-2019-6260 test tool Andrew Jeffery
2019-02-21 3:40 ` Gunnar Mills
2019-02-21 3:56 ` Andrew Jeffery [this message]
2019-02-24 23:10 ` Andrew Jeffery
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=16fc4075-fd43-4d3a-b0be-1e2239e8085e@www.fastmail.com \
--to=andrew@aj.id.au \
--cc=bradleyb@fuzziesquirrel.com \
--cc=gmills@linux.vnet.ibm.com \
--cc=openbmc@lists.ozlabs.org \
/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.