From: Junqian Gordon Xu <xjqian@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE.dev roadworks notification
Date: Tue, 19 Feb 2008 22:12:49 -0500 [thread overview]
Message-ID: <47BB9AB1.4040804@gmail.com> (raw)
In-Reply-To: <1203419692.21824.35.camel@dax.rpnet.com>
On 02/19/2008 06:14 AM, Richard Purdie wrote:
> On a similar note, I'll be doing some work on packaged staging over the
> next few weeks. Again, its been agreed that its in the interests of
> OE.dev on many occasions and now I/we have a chance for action which I'm
> planing to make good use of it.
The following bug (typo) was detected only with INHERIT +=
"packaged-staging2", which is good, however the error message is too
misleading to decipher. As you are on it, you may want to take a look to
see if there is a way to provide a saner error message.
http://lists.linuxtogo.org/pipermail/openembedded-commits/2008-January/011276.html
Regards
Gordon
next prev parent reply other threads:[~2008-02-20 3:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 11:14 OE.dev roadworks notification Richard Purdie
2008-02-19 11:30 ` Graeme Gregory
2008-02-19 12:07 ` Jeremy Lainé
2008-02-20 22:37 ` Leon Woestenberg
2008-02-21 9:57 ` Koen Kooi
2008-02-25 21:05 ` Leon Woestenberg
2008-02-20 3:12 ` Junqian Gordon Xu [this message]
2008-02-20 3:14 ` Junqian Gordon Xu
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=47BB9AB1.4040804@gmail.com \
--to=xjqian@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox