From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] m4: Drop unused/unreferenced patch
Date: Wed, 16 Dec 2015 09:56:08 +0000 [thread overview]
Message-ID: <1450259768.13505.99.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKpCU+5tM0UzjmxyARRCqP_VSQ0X1nnF3mDNYCtFoVjwuQ@mail.gmail.com>
On Tue, 2015-12-15 at 22:13 -0200, Otavio Salvador wrote:
> On Tue, Dec 15, 2015 at 8:27 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> Is there a way to have a task, like fetchall, which checks for
> non-referenced metadata files? This would help to avoid this to
> happen
> in future.
Its a nice idea, the complexity is we have patches which can be native
specific, libc specific, machine specific and so on.
I guess if there were some bitbake API to pull out 'all possible
overrides', we might be able to come up with a definitive list and do
some checks based on that. Its not a simple problem and its also not a
top priority issue right now with available resources. Might be an idea
to open an enhancement bug for it though?
Cheers,
Richard
prev parent reply other threads:[~2015-12-16 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 22:27 [PATCH] m4: Drop unused/unreferenced patch Richard Purdie
2015-12-16 0:13 ` Otavio Salvador
2015-12-16 2:56 ` Paul Eggleton
2015-12-16 9:56 ` Richard Purdie [this message]
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=1450259768.13505.99.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@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