On Fri, Nov 19, 2010 at 8:07 PM, Srdjan Todorovic < todorovi...@googlemail.com> wrote:
> On 19 November 2010 19:12, Bond <jamesbond.2...@gmail.com> wrote: > > On Fri, Nov 19, 2010 at 11:13 PM, Alison Chaiken <alchai...@gmail.com> > wrote: > >> Anuz, I think your document is right on-target. I would just add, > >> "Don't ask for help with basic C programming." Yes, there are lots > >> of idioms in the kernel that are not found elsewhere in C, and asking > >> about those is on-topic, but questioners should not (intentionally) > >> ask questions that will be answered by consulting K&R. > > I totally agree with Alison's reply. This is not a place to discuss > general / beginner C programming topics, and we should make sure this > guide makes that clear. > > > It would be a difficult task to mention what structures or data types > > occur again and again which are not present in K &R to make a wiki > > page on kernelnewbies and point to it but this would be worth than > > making a lecture note and when some one asks some question which is a > > common fault then give them a 5 page lecture to read that doc. > > I do not see any value in such a doc most of the people would be happy > > with a guide of how to ask questions smart way. > > So are you agreeing or disagreeing with Anuz's (cool) document and > Alison's suggestion? > > I have seen this kind of problem in another mailing list, and the > issue seems to be more of a language barrier than technical > understanding of the topic. > > I doubt any FAQ or lecture will help in that situation, unless there > are translations to other languages. > > I like so far of what I've read of Anuz's document - though it could > be tidied up so that you don't have to turn on word-wrapping to be > able to read it. > oh! I totally missed the fact it would be a pain to read(vim is not the nicest way to write such document). I will line-wrap it for more clarity.
