From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 14 Sep 2016 07:57:08 +0200 (CEST) From: Julia Lawall To: Joe Perches In-Reply-To: <1473819862.32273.16.camel@perches.com> Message-ID: References: <20160913194520.GA8071@cloud> <20160913140322.3ccad27c@lwn.net> <4691924.fimvUkKjuv@vostro.rjw.lan> <20160914020332.GA9558@cloud> <1473819862.32273.16.camel@perches.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: ksummit-discuss@lists.linux-foundation.org, ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [CORE TOPIC] checkpatch/Codingstyle and trivial patch spam List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 13 Sep 2016, Joe Perches wrote: > On Tue, 2016-09-13 at 19:03 -0700, Josh Triplett wrote: > > "Do > > not mass-reformat existing code, even if it doesn't follow these > > guidelines; doing so creates noise in version control history and makes > > patches fail to apply." > > It also could be useful to somehow separate newer, more actively > developed code from the old stuff that should remain more static. > > Old code should really only get code improvements like API changes, > size reductions, constifications, performance improvements and bug > fixes. > > Maybe change the MAINTAINERS sections S: entries to have more > comprehensive descriptions of what types of changes are acceptable > for each section. > > Right now it's > > S: Supported > or > S: Maintained > > Or maybe add something like a new entry for what types of changes > are acceptable with a default of "none" What types of changes are unacceptable? What types of changes are acceptable could be difficult to summarize in advance. julia > C: Whitespace and Style > > checkpatch could warn when changes are proposed for code that should > remain static. > _______________________________________________ > Ksummit-discuss mailing list > Ksummit-discuss@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss >