From: Julia Lawall <julia.lawall@lip6.fr>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Joe Perches <joe@perches.com>,
ksummit-discuss@lists.linux-foundation.org,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] checkpatch/Codingstyle and trivial patch spam
Date: Wed, 14 Sep 2016 21:26:19 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1609142120090.3347@hadrien> (raw)
In-Reply-To: <20160914143934.4nkdur7ivgywyfrt@thunk.org>
On Wed, 14 Sep 2016, Theodore Ts'o wrote:
> On Wed, Sep 14, 2016 at 04:35:06PM +0200, Julia Lawall wrote:
> >
> > The --force is only required for non-staging code? If it is required for
> > staging code, then we will have to document it in the outreachy tutorial,
> > and then all the (non-outreachy) newbies who look at the tutorial will
> > know about it...
>
> The whole point of the option is to try to discourage people from
> sending white-space (or only style-only) patches. So I'm not so sure
> that it would be such a tragedy if people like (for example) Markus
> Elfing or Nick Krause don't find out about the --force option right
> away. Given that outreachy folks are encouraged to work on staging
> code anyway, would it make a difference to them?
People other than outreachy applicants may look at the outreachy tutorial.
It is even written that way in some cases. I guess that checkpatch could
detect whether -f is used on a staging driver and not require --force if
that is the case. This would have the other desirable benefit of reducing
the chance that outreachy applicants will send patches on non-staging
code.
julia
next prev parent reply other threads:[~2016-09-14 19:26 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
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 [this message]
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=alpine.DEB.2.10.1609142120090.3347@hadrien \
--to=julia.lawall@lip6.fr \
--cc=joe@perches.com \
--cc=ksummit-discuss@lists.linux-foundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tytso@mit.edu \
/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