From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: akuster808 <akuster808@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] build summary: add gcc version being used.
Date: Wed, 20 Jul 2016 15:53:52 +0100 [thread overview]
Message-ID: <1469026432.23580.14.camel@linuxfoundation.org> (raw)
In-Reply-To: <578F8DA0.3020200@gmail.com>
On Wed, 2016-07-20 at 07:41 -0700, akuster808 wrote:
> I noticed this patch was being carried in mut builds and no is
> missing.
>
> does that mean this is rejected?
I've been meaning to reply to this. I can certainly understand why we
might want to add things to the summary, equally, we do need to
carefully select what we display here. My own personal belief is that
we need to rationalise what is there as there are some key things
missing which are probably more important than gcc version.
With gcc version, I'm very tempted to try and get OE-Core back to a
single gcc version rather than try and put better debug messages in
place as we never intended to have multiple versions.
So I guess I'd prefer we try and rationalise things a bit and put more
thought into this...
Cheers,
Richard
next prev parent reply other threads:[~2016-07-20 14:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 15:29 [PATCH 0/2] Add gcc version and tclibc to build summary Armin Kuster
2016-06-22 15:29 ` [PATCH 1/2] build summary: add gcc version being used Armin Kuster
2016-07-20 14:41 ` akuster808
2016-07-20 14:53 ` Richard Purdie [this message]
2016-06-22 15:29 ` [PATCH 2/2] build summary: add TCLIBC " Armin Kuster
2016-06-22 16:52 ` [PATCH 0/2] Add gcc version and tclibc to build summary Khem Raj
2016-06-22 17:05 ` akuster808
2016-06-22 17:21 ` Khem Raj
2016-06-25 15:30 ` akuster808
[not found] ` <CAMKF1srkQ00SZVk2T3tp-o=ZBO8Xstv6JmZthksCE=geBfw1jw@mail.gmail.com>
[not found] ` <CAMKF1spToGmm0bLgqWu51bBKx6-NuN0ru9LAnEq7P3egKC5B2Q@mail.gmail.com>
2016-06-25 15:45 ` Khem Raj
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=1469026432.23580.14.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@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