From: Joe Perches <joe@perches.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: ksummit-discuss@lists.linux-foundation.org,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] checkpatch/Codingstyle and trivial patch spam
Date: Tue, 13 Sep 2016 23:43:22 -0700 [thread overview]
Message-ID: <1473835402.32273.23.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1609140830550.3395@hadrien>
On Wed, 2016-09-14 at 08:35 +0200, Julia Lawall wrote:
> On Tue, 13 Sep 2016, Joe Perches wrote:
> > On Wed, 2016-09-14 at 07:57 +0200, Julia Lawall wrote:
> > > What types of changes are unacceptable?
> >
> > It's a mixed bag.
> >
> > Some maintainers reject all "style/whitespace changes".
> > Some maintainers reject global consistency patches like
> > int -> bool conversions.
> > Some maintainers reject literal -> #define changes like
> > 1 -> true and 0 -> false for booleans.
> >
> > Some of those maintainers are IMO misguided.
> Sorry, I just meant that you said that the section should list the kinds
> of changes that are acceptable. But it seems more feasible to say what
> kinds of changes are not acceptable. Then one would need a standardized
> language for describing what those unacceptable changes are.
> julia
>
<shrug>
Is there really a difference in whatever grammar would be
necessary between what's acceptable and what's not acceptable?
It's still a classification problem.
next prev parent reply other threads:[~2016-09-14 6:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 18:58 Christian Borntraeger
2016-09-13 19:18 ` Joe Perches
2016-09-13 19:45 ` Josh Triplett
2016-09-13 20:03 ` Jonathan Corbet
2016-09-13 22:14 ` Joe Perches
2016-09-14 5:29 ` Julia Lawall
2016-09-13 23:49 ` Rafael J. Wysocki
2016-09-14 2:03 ` Josh Triplett
2016-09-14 2:24 ` Joe Perches
2016-09-14 5:57 ` Julia Lawall
2016-09-14 6:27 ` Joe Perches
2016-09-14 6:35 ` Julia Lawall
2016-09-14 6:43 ` Joe Perches [this message]
2016-09-14 17:11 ` Alexandre Belloni
2016-09-15 16:33 ` Jonathan Cameron
2016-09-14 11:54 ` Greg KH
2016-09-14 14:23 ` Joe Perches
2016-09-14 14:32 ` Greg KH
2016-09-14 14:35 ` Julia Lawall
2016-09-14 14:39 ` Theodore Ts'o
2016-09-14 19:26 ` Julia Lawall
2016-09-14 14:51 ` Joe Perches
2016-09-14 19:30 ` Julia Lawall
2016-09-14 14:51 ` Joe Perches
2016-09-14 14:45 ` Guenter Roeck
2016-09-14 15:13 ` Joe Perches
2016-09-14 19:46 ` Guenter Roeck
2016-09-14 18:04 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1473835402.32273.23.camel@perches.com \
--to=joe@perches.com \
--cc=julia.lawall@lip6.fr \
--cc=ksummit-discuss@lists.linux-foundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox