Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] distro_features_check: expand with MACHINE_FEATURES and COMBINED_FEATURES, rename
Date: Fri, 22 Nov 2019 18:38:10 -0500	[thread overview]
Message-ID: <20191122233810.GO4735@denix.org> (raw)
In-Reply-To: <20191122231639.GN4735@denix.org>

On Fri, Nov 22, 2019 at 06:16:39PM -0500, Denys Dmytriyenko wrote:
> On Fri, Nov 22, 2019 at 11:10:14PM +0000, Richard Purdie wrote:
> > On Fri, 2019-11-22 at 23:58 +0100, Andreas Müller wrote:
> > > Whatever this patch does renaming does nothing but causing me lots of
> > > useles (rebasing) efforts. To me ist is simlpy the worst patch of
> > > this
> > > year and thanks for blocking me with this. I am really really
> > > upset!!!!!!!
> > 
> > FWIW you can probably unblock yourself by adding a local copy of the
> > compatibility bbclass with the warning removed. That will then let you
> > fix the fallout at a time of your choosing.
> 
> I thought warning would be relatively harmless... Why would it be blocking?
> Do you want this to be a notice instead?
> 
> 
> > I was in two minds about the change to be honest but nobody commented
> > in review and I get really tired of a reputation for saying "no" to
> > "everything". What probably swung the balance is the ways you can work
> > around the change at least temporarily.
> 
> I was also surprised by relative silence in review. Plus, it was in 
> master-next for over a week and nobody complained either...

And to be fair, this is almost right after the release, so is the best time 
for such invasive changes - I did wait and held off submitting it for several 
months to not disrupt the release process!
So such overreaction is rather unwarranted...

-- 
Denys


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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15  0:40 [PATCH v2] distro_features_check: expand with MACHINE_FEATURES and COMBINED_FEATURES, rename Denys Dmytriyenko
2019-11-22 22:58 ` Andreas Müller
2019-11-22 23:10   ` Richard Purdie
2019-11-22 23:16     ` Denys Dmytriyenko
2019-11-22 23:38       ` Denys Dmytriyenko [this message]
2020-09-22 15:11         ` [OE-core] " Martin Jansa
2019-11-22 23:39       ` Andreas Müller
2019-11-22 23:15   ` Denys Dmytriyenko

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=20191122233810.GO4735@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox