From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Cc: "Eggleton, Paul" <paul.eggleton@intel.com>,
"sanil.kumar" <sanil.kumar@huawei.com>
Subject: Fixing Warnings
Date: Fri, 16 Mar 2012 14:07:56 +0000 [thread overview]
Message-ID: <1331906876.18586.186.camel@ted> (raw)
We need to ensure we don't overlap with the warning message fixing work.
I've created:
https://wiki.yoctoproject.org/wiki/Warning_Fixing
which has a list of the remaining warnings I know about and has an
indication of who (if anyone) is addressing them. Please check there
before working on any given warning message.
The good news is we're down to about 115 of them for world assuming the
pending patches merge.
I'm tempted to turn off the exec_prefix cross linkage warnings in the
release branch for this release since the fixes for those could be too
invasive to take the risk on at this point in the release cycle and most
users probably don't need to see those warnings. Those warnings should
be treated as the lowest priority.
Cheers,
Richard
reply other threads:[~2012-03-16 14:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1331906876.18586.186.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@intel.com \
--cc=sanil.kumar@huawei.com \
/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