From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] libunwind: new recipe
Date: Fri, 19 Mar 2010 12:30:04 +0000 [thread overview]
Message-ID: <1269001804.14566.1450.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <ac9c93b11003190341l3a971c41oe49170670498b104@mail.gmail.com>
On Fri, 2010-03-19 at 11:41 +0100, Frans Meulenbroeks wrote:
> I was left with about 380 vars. See the list attached.
> Guess most of them are undocumented (and actually 380 seems an awful lot to me).
That's an interesting list. It's hard to say how many of those are
actually intended for public consumption.
Some of them, like KERNEL_VERISON (sic), presumably are bogus and serve
no useful purpose. Some of them look like they are probably meant to be
internal to the class in question and shouldn't be used or set by
anything else.
But you're right, more documentation would be better.
p.
next prev parent reply other threads:[~2010-03-19 12:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 20:22 [PATCH] libunwind: new recipe Steffen Sledz
2010-03-17 23:04 ` Khem Raj
2010-03-19 9:29 ` Paul Menzel
2010-03-19 10:09 ` Koen Kooi
2010-03-19 10:26 ` Richard Purdie
2010-03-19 10:41 ` Frans Meulenbroeks
2010-03-19 12:30 ` Phil Blundell [this message]
2010-03-19 12:55 ` Steffen Sledz
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=1269001804.14566.1450.camel@mill.internal.reciva.com \
--to=philb@gnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox