Dear Gerhard, In message <[email protected]> you wrote: > > > Please capitalize, yes, there's a strong policy when communicating with > > other > > people ;-) > > Such a policy appears to strongly depend on individual projects, > as people's perception is not universally identical. Speaking
There are some genral netiquette rules, though. See for example [1]; I really recommend to follow that advice. [1] http://www.catb.org/~esr/faqs/smart-questions.html#writewell > I always assumed that there is a difference between documentation > and "non-documentation" (source code comments, commit messages), > where the latter are not prose and don't pretend to be. I can't parse that. What makes you think that comments in the source code or commit messages are NOT documentation as well? Actually this is extremely important documentation (and often the only one that there is), so it deserves all case to be done well. > But now that I learned that this is the policy in Yocto and thus > in ELDK, there's no problem following it. Just did not know yet. Please drop the idea that this is something that would be project specific. Even if you find examples where other people write sloppy text and get through with it, you should not look at such bad examples. Please always try to write clear and precise text. The people who invest time to read what you wrote deserve that much. Thanks. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [email protected] Things are not as simple as they seem at first. - Edward Thorp _______________________________________________ eldk mailing list [email protected] http://lists.denx.de/mailman/listinfo/eldk
