From: "Adrian Bunk" <bunk@stusta.de>
To: akuster <akuster808@gmail.com>
Cc: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] meta-python Dunfell branch maintenance
Date: Mon, 29 Jun 2020 18:19:51 +0300 [thread overview]
Message-ID: <20200629151951.GA7038@localhost> (raw)
In-Reply-To: <c1502c01-c4c8-b05c-5db1-979b0d335b38@gmail.com>
On Mon, Jun 29, 2020 at 07:59:13AM -0700, akuster wrote:
> Hello all,
>
> I have notice many meta-python3 recipes are having their .inc files
> being consolidated. I am considering backporting those consolidations
> that are bug fix only
Those consolidations can never be "bug fix only" - part of a recipe in
an .inc file is not a bug.
> so that maintenance moving forward is easier.
>
> Any concerns from the community on taking that route where appropriate?
I wouldn't see it appropriate for a stable branch in most cases.
If you are backporting other changes for a recipe that were done in
master on top of such a change this approach sounds like an option, but
in the normal case that the recipe is never touched for other reasons in
a stable branch I do not see the benefits of making such unnecessary changes.
> regards,
> Armin
cu
Adrian
next prev parent reply other threads:[~2020-06-29 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 14:59 meta-python Dunfell branch maintenance akuster
2020-06-29 15:19 ` Adrian Bunk [this message]
2020-06-30 15:07 ` [oe] " Khem Raj
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=20200629151951.GA7038@localhost \
--to=bunk@stusta.de \
--cc=akuster808@gmail.com \
--cc=openembedded-devel@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 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.