From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC][meta-oe][meta-toolchain][PATCH] meta-toolchain: populate with gcc and binutils from meta-oe
Date: Thu, 22 Mar 2012 11:27:59 +0100 [thread overview]
Message-ID: <jkeurg$cb8$1@dough.gmane.org> (raw)
In-Reply-To: <FD67157F-A373-42D4-93CE-3FF8A142CA56@dominion.thruhere.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 22-03-12 11:15, Koen Kooi schreef:
>
> Op 22 mrt. 2012, om 11:07 heeft Martin Jansa het volgende geschreven:
>
>> On Thu, Mar 22, 2012 at 11:01:39AM +0100, Koen Kooi wrote:
>>> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
>>
>> Why not move them?
>
> This was done to have people test it in the oe-core + meta-toolchain
> setup. And to avoid bblayers.conf conflicts
>
>> Or create stub of meta-toolchain in 1st patch for people to add it to
>> bblayers and then move it in 2nd.
>
> That sounds like a better way to do it. Maybe Eric will do that in his
> patchset :)
I don't have a strong opinion on this and if Eric wants me to respin the RFC
I'll gladly do that. But I would prefer that I can be lazy and just merge
other peoples patches :)
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQIcBAEBAgAGBQJPav6tAAoJEHZqAkdh1vT6zcYP/2CHId7lbxYDDC2sMa8fb7Nt
+FIRDOIDyF+laMlAwuMMuN0NN6228mxnxmCD0tkrcq6wJnaBJ5+LKkHmwYAUnjrY
q4ayrZTWGGTIkcYVpeizZCh15AomFLuBzTKP/XdOUESQscheV/zdWgT26hqVRQrS
3spk1oS2kzevvmmSqjxBxUUmFMGi85ZcjcsN0aIUpf11+dkU1SpIrGIr7BnybGr/
FEXzWFCHRtSsmI9J6n6dhrDrm3d2fMxV+9AbqeE1SQbaGV+lA+vag5aDhYdfpbOF
S+aPYCCm0rrDsFvNqYTq/IU5Fx2/WUa6zHZlnWoUd1iyvPOaiRezGS7diQfV0R3v
OxCy/75j2cq2ofPebJWG5zGhDvDk9TWW6BqC791WAm9VJjD4ztFhvtE12nXYqIoC
9TDAoURNPNX4FBnLQkX0p6Luo4P5c9hgo6BBwQZR2fwmov4R1nq91AFsMrKJRyxh
VCAqSbzaTJq1zJhh5UZNwRB0SyvDgLbi58NFVOGItX/DUUCUbjC+/aXyIV4Czf75
OeQ29f8vPvzed9wryg8rdogccbuJ2QY9MGaBfEkUOwBNt/HzhYFY4WpcGvvpqsqA
VzPe0wst0+ncGdB2/MewNETXPGy3Mp8xvUTvlabaXnOzRmZqUxkqONVnSZkQqGOy
BCepRNuESem5ktLHCKQS
=5mMh
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-03-22 10:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 10:01 [RFC][meta-oe][meta-toolchain][PATCH] meta-toolchain: populate with gcc and binutils from meta-oe Koen Kooi
2012-03-22 10:07 ` Martin Jansa
2012-03-22 10:12 ` Eric Bénard
2012-03-22 10:20 ` Martin Jansa
2012-03-22 10:15 ` Koen Kooi
2012-03-22 10:27 ` Koen Kooi [this message]
2012-03-22 12:23 ` Khem Raj
2012-03-22 12:32 ` Koen Kooi
2012-03-22 10:09 ` Eric Bénard
2012-03-22 14:33 ` Paul Eggleton
2012-03-22 14:36 ` Paul Eggleton
2012-03-22 16:08 ` 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='jkeurg$cb8$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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