From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: Yocto Project 1.4 Planning Process
Date: Wed, 03 Oct 2012 17:20:53 +0100 [thread overview]
Message-ID: <506C65E5.4070003@linaro.org> (raw)
In-Reply-To: <1349280226.18301.50.camel@ted>
W dniu 03.10.2012 17:03, Richard Purdie pisze:
> Whilst I appreciate people are concentrating on 1.3, we do also need
> to think about planning 1.4.
> Questions are more than welcome, as is feedback about this process.
Before adding it to bugzilla or wiki I would like to list few things
which would be usable during adding new architecture (maybe missed them).
1. A way to automatical upload logs after build - selection all/failed
one would be extra.
2. A way to collect preprocessed files in case of gcc ICE.
3. Option to automatically rebuild ICEd recipe with PARALLEL_MAKE
disabled so it is easier to notice where it ICEd.
prev parent reply other threads:[~2012-10-03 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 16:03 Yocto Project 1.4 Planning Process Richard Purdie
2012-10-03 16:20 ` Marcin Juszkiewicz [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=506C65E5.4070003@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.