All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] clang-format for v5.3-rc8
Date: Wed, 04 Sep 2019 16:34:58 -0700	[thread overview]
Message-ID: <6806d25a240cd80ebd265fcf5f02496852027bed.camel@perches.com> (raw)
In-Reply-To: <20190904182949.GA22025@gmail.com>

On Wed, 2019-09-04 at 20:29 +0200, Miguel Ojeda wrote:
> Hi Linus,
> 
> Please pull this trivial update for the .clang-format file.
> 
> Cheers,
> Miguel
> 
> The following changes since commit a55aa89aab90fae7c815b0551b07be37db359d76:
> 
>   Linux 5.3-rc6 (2019-08-25 12:01:23 -0700)
> 
> are available in the Git repository at:
> 
>   https://github.com/ojeda/linux.git tags/clang-format-for-linus-v5.3-rc8
> 
> for you to fetch changes up to 52d083472e0b64d1da5b6469ed3defb1ddc45929:
> 
>   clang-format: Update with the latest for_each macro list (2019-08-31 10:00:51 +0200)
> 
> ----------------------------------------------------------------
> clang-format update for 5.3
> 
> ----------------------------------------------------------------
> Miguel Ojeda (1):
>       clang-format: Update with the latest for_each macro list
> 
>  .clang-format | 17 ++++++++++++++---
>  1 file changed, 14 insertions(+), 3 deletions(-)

It's a long, long list.

$ git grep -P -h '^\s*#\s*define\s+\w*for_each\w*' | \
  grep -P -oh '\w+for_each\w*' | sort | uniq | wc -l
491

Isn't there some way to regexes or automate this?

Maybe just:
$ git grep -P -h '^\s*#\s*define\s+\w*for_each\w*' | \
  grep -P -oh '\w+for_each\w*' | sort | uniq > somefile...




  reply	other threads:[~2019-09-04 23:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04 18:29 [GIT PULL] clang-format for v5.3-rc8 Miguel Ojeda
2019-09-04 23:34 ` Joe Perches [this message]
2019-09-05  0:05   ` Miguel Ojeda
2019-09-05 21:15 ` pr-tracker-bot

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=6806d25a240cd80ebd265fcf5f02496852027bed.camel@perches.com \
    --to=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.