All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mikko.Rapeli@bmw.de
Cc: openembedded-core@lists.openembedded.org
Subject: Re: maintaining sumo (was Re: [PATCH][thud] cve-check: backport rewrite from master)
Date: Mon, 11 Nov 2019 11:22:35 +0000	[thread overview]
Message-ID: <ec1a8e75a2c5eb4dc341501f1f919aa070c8c226.camel@linuxfoundation.org> (raw)
In-Reply-To: <20191107075931.GD2398@hiutale>

On Thu, 2019-11-07 at 07:59 +0000, Mikko.Rapeli@bmw.de wrote:
> I need to maintain sumo in a project for a while longer so I can
> publish that work. The CVE checker patches are just a start.
> 
> Providing funding for Yocto Project LTS work is possible but a lot
> harder for me to do. Testing and publishing patches is much easier.
> 
> Could you clarify Yocto Project side answers to these questions:

I just want to be clear I'm not ignoring this but I need the TSC to
figure a few things out before we can answer this. I suspect that may
take a short while as its tied into the discussions about LTS and that
rests with the YP governing board at the moment.

We need to consistently handle everything with a plan so patience with
this is appreciated!

Cheers,

Richard



  parent reply	other threads:[~2019-11-11 11:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 12:23 [PATCH][thud] cve-check: backport rewrite from master Ross Burton
2019-11-06 14:59 ` Ryan Harkin
2019-11-06 16:06   ` Mikko.Rapeli
2019-11-06 17:53     ` Richard Purdie
2019-11-07  7:59       ` maintaining sumo (was Re: [PATCH][thud] cve-check: backport rewrite from master) Mikko.Rapeli
2019-11-07 10:41         ` Ryan Harkin
2019-11-11  8:08           ` Mikko.Rapeli
2019-11-11 10:54             ` Ryan Harkin
2019-11-11 11:22         ` Richard Purdie [this message]
2019-11-11 16:21         ` akuster808

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=ec1a8e75a2c5eb4dc341501f1f919aa070c8c226.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Mikko.Rapeli@bmw.de \
    --cc=openembedded-core@lists.openembedded.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.