From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] CVE tracker: questions
Date: Thu, 21 Mar 2019 09:15:41 +0000 [thread overview]
Message-ID: <1553159741.3557.1.camel@codethink.co.uk> (raw)
In-Reply-To: <2544745.Y8d6tg5VCe@linux-3zh6>
On Wed, 2019-03-20 at 16:01 +0100, Agustin Benito Bethencourt wrote:
> Hi Ben,
>
> during the past face to face TSC meeting that took place in N?rnberg, there?
> were two questions about the CVE tracker you have done that would need some?
> more details from you that what I provided back then.
>
> Is the CVE tracker in a state that can be used by CIP Members?
I think so, yes.
> If it is, under which conditions? Does it work for any kernel or needs to be?
> tuned?
It currently only works for mainline and stable branches. I have an
open issue to add support for CIP branches.
> Can we advertise the CVE tracker in the coming events in Japan in July?
That would be fine with me.
> I would like to add the following questions
>
> Is this a work you plan to maintain in the coming future?
So long as I'm working for CIP, yes.
> Would it be valuable to somehow keep the outcome of the tracker in Gitlab so?
> we can keep track of the patches that require attention, so the Kernel?
> Maintenance team can also get involved?
>
> Would it work for -rt ?
Not currently, no. If and when I add support for CIP branches, I
expect -rt branches to be supportable in the same way.
Ben.
--
Ben Hutchings, Software Developer ? Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
prev parent reply other threads:[~2019-03-21 9:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 15:01 [cip-dev] CVE tracker: questions Agustin Benito Bethencourt
2019-03-21 9:15 ` Ben Hutchings [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=1553159741.3557.1.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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.