| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 8 Jan 2008 20:21:42 +0100 From: Sam Ravnborg <sam@...nborg.org> To: Daniel Walker <dwalker@...sta.com> Cc: Theodore Tso <tytso@....edu>, Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org, apw@...dowen.org, akpm@...ux-foundation.org Subject: Re: [PATCH] Deprecate checkpatch.pl --file > > What I was saying in my first email was we can throttle "patches" > arbitrarily (I think Andrew/Linus even have a merge period for these > types of patches) .. So that's not the issue .. I feel style clean ups > are fundamentally good.. So what we don't want to do is discourage the > creation of good patches, which is what I think Andi is doing.. The way I read this: +WARNING: Using --file mode. Please do not send patches to linux-kernel +that change whole existing files if you did not significantly change most +of the the file for other reasons anyways or just wrote the file newly +from scratch. Pure code style patches have a significant cost in a +quickly changing code base like Linux because they cause rejects +with other changes. does not discourage the creation of good patches. But is discourage the creation of pure clean-up patches because it may have a disturbing effect on several other peoples work. Sam -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists