From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: Philip Balister <philip@balister.org>,
openembedded-core@lists.openembedded.org
Subject: Re: Stable branch rules [Was: Re: [PATCH][jethro] glibc-locale: fix QA warning]
Date: Tue, 09 Feb 2016 15:40:52 +0000 [thread overview]
Message-ID: <1455032452.6918.13.camel@linux.intel.com> (raw)
In-Reply-To: <56B9FCA8.7010303@balister.org>
On Tue, 2016-02-09 at 09:50 -0500, Philip Balister wrote:
> On 02/08/2016 10:22 AM, Joshua G Lock wrote:
> > On Sun, 2016-02-07 at 22:43 +0000, Richard Purdie wrote:
> > > 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.
> >
> > I made an attempt at starting to documenting that requirement:
> > https://wiki.yoctoproject.org/wiki/index.php?title=Stable_branch_ma
> > inte
> > nance&diff=17480&oldid=17028
> >
> > 'Patches' welcome.
>
> Does this belong on the Yocto Project or OpenEmbedded wikis? Hunting
> both is getting annoying.
I edited the guidelines where they currently exist. I'll be more than
happy to move this to the OE wiki, but I'd rather do that once we have
something that people can agree.
Regards,
Joshua
next prev parent reply other threads:[~2016-02-09 15:40 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 ` Stable branch rules [Was: Re: [PATCH][jethro] glibc-locale: fix QA warning] Richard Purdie
2016-02-08 4:23 ` [Openembedded-architecture] " 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 [this message]
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=1455032452.6918.13.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philip@balister.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