From: alexander.kanavin@linux.intel.com
To: "Martin Jansa" <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] webkitgtk: add REQUIRED_DISTRO_FEATURES
Date: Tue, 22 Sep 2015 17:24:21 +0300 (EEST) [thread overview]
Message-ID: <60704.10.252.48.86.1442931861.squirrel@linux.intel.com> (raw)
In-Reply-To: <20150922131738.GA2388@jama>
>> Why can't the tools figure out which recipes should be excluded from
>> builds without explicit annotations?
>
> See discussion around this change on ML and please don't remove stuff
> just because you don't know/remember why it was added without at least
> using "git blame" to read commit which introduced it.
Fair enough. What about adding new recipes? How is one supposed to figure
out whether there are required distro features to list?
Alex
next prev parent reply other threads:[~2015-09-22 14:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 14:01 [PATCH] webkitgtk: add REQUIRED_DISTRO_FEATURES Martin Jansa
2015-09-21 16:01 ` Alexander Kanavin
2015-09-21 16:49 ` Burton, Ross
2015-09-22 11:12 ` alexander.kanavin
2015-09-22 13:17 ` Martin Jansa
2015-09-22 14:24 ` alexander.kanavin [this message]
2015-09-21 18:57 ` 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=60704.10.252.48.86.1442931861.squirrel@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox