From: Sylvestre Ledru <sylvestre.ledru@scilab.org>
To: Joe Perches <joe@perches.com>
Cc: Andy Whitcroft <apw@canonical.com>,
Andrew Morton <akpm@linux-foundation.org>,
Daniel Walker <dwalker@fifo99.com>,
linux-kernel@vger.kernel.org
Subject: Re: Usage of checkpatch.pl for other projects
Date: Sun, 22 Aug 2010 22:50:29 +0200 [thread overview]
Message-ID: <1282510229.10764.2972.camel@zlarin> (raw)
In-Reply-To: <1282062762.24541.98.camel@Joe-Laptop>
Le mardi 17 août 2010 à 09:32 -0700, Joe Perches a écrit :
> On Tue, 2010-08-17 at 18:16 +0200, Sylvestre Ledru wrote:
> > Le mardi 17 août 2010 à 17:01 +0100, Andy Whitcroft a écrit :
> > > What sort of differences are you thinking about.
> > At first, mainly basic things like space or not before a brace, if a
> > brace should be on the same line as the if or not, etc. This kind of
> > basic things.
>
> It might be better to use a script that uses
> a combination of patch, indent with some
> project specific options and diff to highlight
> how a proposed patch might vary from project
> coding standards.
This might be a good way to start.
We could also create a configuration file with default being the Linux
Kernel's coding styles.
Sylvestre
--
-------------------------
Sylvestre Ledru
-------------------------
The Scilab Consortium
Digiteo
Domaine de Voluceau
Rocquencourt - B.P. 105
78153 Le Chesnay Cedex
France
next prev parent reply other threads:[~2010-08-23 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 9:37 Usage of checkpatch.pl for other projects Sylvestre Ledru
2010-08-17 16:01 ` Andy Whitcroft
2010-08-17 16:16 ` Sylvestre Ledru
2010-08-17 16:32 ` Joe Perches
2010-08-22 20:50 ` Sylvestre Ledru [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-13 8:35 Sylvestre Ledru
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=1282510229.10764.2972.camel@zlarin \
--to=sylvestre.ledru@scilab.org \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=dwalker@fifo99.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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