On Fri, 23 May 2008 23:23:39 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:Don't think so. Unrelated changes are well-known poor-form. I do think that if one is already changing a line which is incorrectly laid out then there's no point in _leaving_ it incorrect. There's no downside to fixing it. That being said, it's often sorely tempting to go hunting down nearby sillinesses. I succumb to that temptation and usually won't complain when others do also, up to a point. mm, not really. Wrong is wrong and if nominal maintainer insists on retaining wrong we have cheery bunfights about it. I think those changes went above and beyond the call. And that is why we have a standard - so that different parts of the kernel do not end up having different appearance due to local preferences. --
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| debian developer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [patch 00/40] 2.6.23-stable review, driver (sans network) changes |
| Roland Dreier | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Arjan van de Ven | Re: [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Natalie Protasevich | [BUG] New Kernel Bugs |
