From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Gary Thomas <gary@mlbassoc.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bitbake.conf/base.bbclass: Drop PRINC support
Date: Tue, 04 Nov 2014 13:24:07 +0000 [thread overview]
Message-ID: <1415107447.23396.27.camel@ted> (raw)
In-Reply-To: <CAP9ODKpQmRo-yXMMURRDU8QpSo1fA4vx+wcXFXuBaT=hOgTC_A@mail.gmail.com>
On Tue, 2014-11-04 at 10:12 -0200, Otavio Salvador wrote:
> On Tue, Nov 4, 2014 at 10:08 AM, Gary Thomas <gary@mlbassoc.com> wrote:
> > Won't this just silently make use of PRINC a no-op? What about
> > the users that had their head in the sand for the last few months
> > but still expect PRINC to have some effect (and maybe don't use
> > PR server)? I would think escalating this to an error would make
> > more sense (and follow other warnings that are now errors).
>
> I agree with Gary, move this to ERROR now and drop in 1.9.
Its been printing warnings since May 2013. I tried to merge this 6
months ago, I was told to wait another release, by you:
http://lists.openembedded.org/pipermail/openembedded-core/2014-March/090169.html
Now I need to keep the patch for another 6 months. This really is taking
too long IMO. I may well get bored and just drop the patch (and forget
any other ideas about trying to cleanup things).
Cheers,
Richard
next prev parent reply other threads:[~2014-11-04 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 11:26 [PATCH] bitbake.conf/base.bbclass: Drop PRINC support Richard Purdie
2014-11-04 12:08 ` Gary Thomas
2014-11-04 12:12 ` Otavio Salvador
2014-11-04 13:24 ` Richard Purdie [this message]
2014-11-04 15:32 ` Otavio Salvador
-- strict thread matches above, loose matches on Subject: below --
2015-05-03 10:37 Richard Purdie
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=1415107447.23396.27.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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