On Friday 06 April 2007 12:16 pm, Jan Engelhardt wrote:
... agree with what I said, since that's exactly what CodingStyle says,
and what essentially every line of kernel code does today. (There are
random spots of brokenness, but they get fixed over time.)
> though I do not speak for
Your eyes are broken then ... or maybe you're focussing exclusively
on code that violates the most basic coding guidelines like:
if (...) {
THAT WAS ONE MORE TAB
}
and
for (...) {
THAT WAS ALSO ONE MORE TAB
}
Come on, stop wasting everyone's time with utter nonsense.
- Indent always uses tabs
- When breaking long lines (including long conditions)
* STILL indent with tabs
* ... and more than one, to be "substantially" more indented
That's what Documentation/CodingStyle says **TODAY** so stop with the flamage.
-
| Greg Kroah-Hartman | [PATCH 008/196] Chinese: add translation of volatile-considered-harmful.txt |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in |
| Andrew Morton | -mm merge plans for 2.6.23 |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Herbert Xu | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Rémi Denis-Courmont | [PATCH 01/14] Phonet global definitions |
