From: Adrian Bunk <bunk@stusta.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] Lower priority of debug messages that should not be shown on the console
Date: Fri, 6 Mar 2020 12:24:20 +0200 [thread overview]
Message-ID: <20200306102420.GB17785@localhost> (raw)
In-Reply-To: <f5a7208c16b4df00445cb280b3a556923c07db97.camel@linuxfoundation.org>
On Mon, Feb 24, 2020 at 09:12:06AM +0000, Richard Purdie wrote:
> On Mon, 2020-02-24 at 07:49 +0200, Adrian Bunk wrote:
> > On Sun, Feb 23, 2020 at 11:53:57PM +0000, Richard Purdie wrote:
>...
> > > I know you didn't mean it this way and we need to track the issues,
> > > I
> > > just don't know how we're going to handle it.
> >
> > From my side the problem is that my initial patch is what I can do
> > with reasonable effort.
>
> Part of the reason I'm highlighting this is that I have a lot of
> feedback that says people don't believe there is any problem with our
> resourcing. Unless I can show where there are issues, its not going to
> change :/.
Why does YP give users false/misleading information regarding security
support of stable and LTS releases despite lack of resources to provide
security support?
There is no reason to believe claims that there would be any problem
with resourcing when the public announcements from YP give the opposite
impression.
> Cheers,
>
> Richard
cu
Adrian
next prev parent reply other threads:[~2020-03-06 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 20:52 [PATCH] Lower priority of debug messages that should not be shown on the console Adrian Bunk
2020-02-22 11:57 ` Andreas Müller
2020-02-22 22:05 ` Adrian Bunk
2020-02-22 15:54 ` Richard Purdie
2020-02-23 19:51 ` Adrian Bunk
2020-02-23 23:53 ` Richard Purdie
2020-02-24 5:49 ` Adrian Bunk
2020-02-24 9:12 ` Richard Purdie
2020-03-06 10:24 ` Adrian Bunk [this message]
2020-03-06 10:47 ` Richard Purdie
2020-03-06 11:18 ` Alexander Kanavin
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=20200306102420.GB17785@localhost \
--to=bunk@stusta.de \
--cc=bitbake-devel@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.