[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180313140037.7717460162192c99775b135e@linux-foundation.org>
Date: Tue, 13 Mar 2018 14:00:37 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: rdunlap@...radead.org, apw@...onical.com, joe@...ches.com,
corbet@....net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] clang-format: add configuration file
On Tue, 13 Mar 2018 00:39:52 +0100 Miguel Ojeda <miguel.ojeda.sandonis@...il.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?
Powered by blists - more mailing lists