On Wed, 23 May 2007 21:15:20 +0200 Rene Herman wrote: > On 05/23/2007 07:04 PM, Randy Dunlap wrote: > > >> That's a good source of confusion. To me, "notime" means something > >> like "don't bother calculating time", instead of the proposed > >> behavior. Can't it be something like 'nologts' (no log timestamps) > >> or nots or notimestamps or nologtime instead? > > > > "nologtime" is OK with me. or does it confuse people in a > > different way? Anyone else? > > The CONFIG option is called CONFIG_PRINTK_TIME. How about "noprintktime"? At > least nicely to the point...
Actually I'm concerned about total kernel command line length, so using option names that are "long" when short will do is not good IMO. I.e., I can easily overflow a 255-byte command line length buffer, so Shorter is Better. However, "when short will do" does not mean making them unreadable or like they mean something else, like "nopkt". --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
