From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Armin Kuster <akuster808@gmail.com>,
openembedded-core@lists.openembedded.org,
liezhi.yang@windriver.com,
openembedded-architecture
<openembedded-architecture@lists.openembedded.org>
Cc: Armin Kuster <akuster@mvista.com>
Subject: Stable branch rules [Was: Re: [PATCH][jethro] glibc-locale: fix QA warning]
Date: Sun, 07 Feb 2016 22:43:23 +0000 [thread overview]
Message-ID: <1454885003.27087.344.camel@linuxfoundation.org> (raw)
In-Reply-To: <1454270130-11287-1-git-send-email-akuster808@gmail.com>
On Sun, 2016-01-31 at 11:55 -0800, Armin Kuster wrote:
> From: Armin Kuster <akuster@mvista.com>
>
> WARNING: QA Issue: glibc-locale: /glibc-binary-localedata-sd
> -in/usr/lib/locale/sd_IN/LC_CTYPE is owned by uid 1000, which is the
> same as the user running bitbake. This may be due to host
> contamination [host-user-contaminated]
>
> fix type
> Signed-off-by: Armin Kuster <akuster@mvista.com>
> ---
> meta/recipes-core/glibc/glibc-locale.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Enough is enough.
I cannot tell whether these patches are in master or not or whether
master needs them or not. Master needs this one, its not in master, its
only being proposed for jethro. Its a mess.
I am therefore not taking any more stable branch patches at all until
we amend the stable branch rules to state that pull requests and
patches clearly state which branches need a fix, or clearly state why
they don't.
Cheers,
Richard
next prev parent reply other threads:[~2016-02-07 22:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 19:55 [PATCH][jethro] glibc-locale: fix QA warning Armin Kuster
2016-02-07 22:43 ` Richard Purdie [this message]
2016-02-08 4:23 ` [Openembedded-architecture] Stable branch rules [Was: Re: [PATCH][jethro] glibc-locale: fix QA warning] Khem Raj
2016-02-08 15:22 ` Joshua G Lock
2016-02-09 14:50 ` Philip Balister
2016-02-09 15:40 ` Joshua G Lock
2016-04-01 12:03 ` [PATCH][jethro] glibc-locale: fix QA warning Martin Jansa
2016-04-01 13:14 ` Richard Purdie
[not found] ` <56FEA982.5040500@mvista.com>
2016-04-02 18:19 ` Martin Jansa
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=1454885003.27087.344.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@gmail.com \
--cc=akuster@mvista.com \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-architecture@lists.openembedded.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox