From: Andrew Morton <akpm@linux-foundation.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: rdunlap@infradead.org, apw@canonical.com, joe@perches.com,
corbet@lwn.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clang-format: add configuration file
Date: Tue, 13 Mar 2018 14:00:37 -0700 [thread overview]
Message-ID: <20180313140037.7717460162192c99775b135e@linux-foundation.org> (raw)
In-Reply-To: <20180312233952.niz2cuz7psv4fe2s@gmail.com>
On Tue, 13 Mar 2018 00:39:52 +0100 Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrote:
> --- a/Documentation/process/4.Coding.rst
> +++ b/Documentation/process/4.Coding.rst
> @@ -58,6 +58,12 @@ can never be transgressed. If there is a good reason to go against the
> style (a line which becomes far less readable if split to fit within the
> 80-column limit, for example), just do it.
>
> +Note that you can use the clang-format tool to help you with these rules
> +and to quickly re-format parts of your code automatically. It is specially
> +useful for new files/code and to spot coding style mistakes. It is also
> +useful to sort #includes, to align variables or comments, to reflow text
> +and other similar tasks.
It would be rather helpful to tell people how to invoke clang-format.
Is it just "clang-format foo.c" or what?
next prev parent reply other threads:[~2018-03-13 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 23:39 Miguel Ojeda
2018-03-12 23:45 ` Joe Perches
2018-03-13 21:00 ` Andrew Morton [this message]
2018-03-13 21:52 ` Miguel Ojeda
2018-03-13 22:29 ` Joe Perches
2018-03-14 0:18 ` Miguel Ojeda
2018-03-14 0:56 ` Miguel Ojeda
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=20180313140037.7717460162192c99775b135e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®