[oe] commit 4d6a63850b4dc7ca2f060aedda26ddf4efa0e5cc

Frans Meulenbroeks fransmeulenbroeks at gmail.com
Wed Jul 7 09:24:02 UTC 2010


2010/7/7 Koen Kooi <k.kooi at student.utwente.nl>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 07-07-10 10:22, Frans Meulenbroeks wrote:
>
>> - I haven't really seen interested from angstrom to support nios2.
>> Feel free to correct me by sending a pointer (preferably referring to
>> the angstrom mailing list)
>
> Both me and Graemo have told you that in that RFC thread, that's 2/3 of
> the angstrom core developers already.

Graeme mentioned that if I asked, it might be added. One might
consider that as interest.
>From you I have not seen a message that I interpreted as interest from
the angstrom side.
(and if that is a misinterpretation from my side, my apologies for that).

Anyway, I have no interest in having a yes/no discussion on whether or
not angstrom has shown interest.
If angstrom wants to support nios2, fine with me. If not, also no problem.

There is a machine.conf. I feel it serves its needs. The rationale why
things are added is well documented. Pinning things in a machine conf
is afaik not in violation with any OE design rule, and also not
uncommon as 100+ pinnings in the machine dir tell me.

But if you feel my machine conf file is totally wrong feel free to
raise the issue with the TSC.
(then again I have not seen too much explanation why this is bad; I
just reread the first post of this thread and there is no explanation
why this is bad; maybe it helps if you consider something is bad, that
you explain why it is bad, instead of just making statements that
things are bad. In general by explaining why something is bad you
create understanding. Saying that something is bad without saying why
is only creating anger and frustration).

Frans.


> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFMNDsUMkyGM64RGpERAo+7AJ0cyzYELBJ/RM4bT6CGG5AwoEYNaQCfVJDf
> EgWdJiOPiLdH3pPCXYUKTWY=
> =5bcf
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>




More information about the Openembedded-devel mailing list