Chris Larson wrote:
On Fri, Jun 4, 2010 at 5:52 AM, Frans Meulenbroeks <
[email protected]> wrote:
Apologies for not replying to the original message, but that one is
already deleted.
Just bumped into this after doing a pull.
A few comments:
I would suggest if doing something like this that it is announced
somewhat more explictly so people are well aware of it. Since it was
brought as a patch it escaped my attention, and in fact it is not only
a patch but also a change of policy.
Personally, I'd think people should always read any patches to the main
classes, including patch.bbclass. Any change to a core class or config file
has the potential for large impact, and it would benefit everyone to be
aware of those things.
That said, I'll be sure to send out an RFC to try to draw more attention to
it next time around.
Also I'd like to suggest to complete the change by also updating the
manual, otherwise this could become confusing.
Yes, I know, I intended (and still do intend) to update the manual, but
haven't gotten to it yet. I apologize for the delay.
Maybe we should start saying "no changing how stuff is documented
WITHOUT changing the documentation". It's not like we keep the docs in
some hard to edit format and I think other projects work the same way.
--
Tom Rini
Mentor Graphics Corporation
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
