On Sun, 23 Jul 2006, Stefan Richter wrote: [..]
Tomasz,yes, we have scripts/Lindent, but it cannot and is not supposed to solve all style issues. Coding style is about _much_ more than whitespace. It includes sensible names, usage of language features...
Yes .. I know about this but it can allow plug some subset of current coding style problems. Prodicing Perfect-Word in sigle step is probably impossible but start this step by step will be probably rationale :)
Look below is it not will be good now start: 1) review current tree for fix/change code allow pass throw indent without errors and commit all neccessary for this changes, 2) produce diff for whole source tree and start disscuss on "are current Lindent script indentation rules are correct or not ?", 3) after prepare acceptable by Linus indent rules set setup kind of moratory for all (co)developers for submitting indentation changes during normal changes submission (month or even half year but IMo shorter will be better), 4) aftter passing moratory date Linus can commit all pending changes in single commit. ?? kloczek -- ----------------------------------------------------------- *Ludzie nie mają problemów, tylko sobie sami je stwarzają* ----------------------------------------------------------- Tomasz Kłoczko, sys adm @zie.pg.gda.pl|*e-mail: [email protected]*
- References:
- [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
- From: [email protected] (Panagiotis Issaris)
- Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
- From: Rolf Eike Beer <[email protected]>
- Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
- From: "Pekka Enberg" <[email protected]>
- Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
- From: Jeff Garzik <[email protected]>
- Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
- From: Stefan Richter <[email protected]>
- Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
- From: "Jesper Juhl" <[email protected]>
- Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
- From: Panagiotis Issaris <[email protected]>
- Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
- From: Pekka J Enberg <[email protected]>
- Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
- From: Stefan Richter <[email protected]>
- Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
- From: Tomasz Kłoczko <[email protected]>
- Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
- From: Stefan Richter <[email protected]>
- Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
- From: Tomasz Kłoczko <[email protected]>
- Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
- From: Jeff Garzik <[email protected]>
- Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
- From: Stefan Richter <[email protected]>
- [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
- Prev by Date: Re: [RFC] Use target filename in BUG_ON and friends
- Next by Date: Re: [PATCH] Cpuset: fix ABBA deadlock with cpu hotplug lock
- Previous by thread: Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
- Next by thread: Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
- Index(es):