All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] clang-format for v5.3-rc8
Date: Thu, 5 Sep 2019 02:05:49 +0200	[thread overview]
Message-ID: <CANiq72nVtTa17pnOhKKjx6NY3eYjU5FcXcN4MxFJkwkwV3+ghQ@mail.gmail.com> (raw)
In-Reply-To: <6806d25a240cd80ebd265fcf5f02496852027bed.camel@perches.com>

On Thu, Sep 5, 2019 at 1:35 AM Joe Perches <joe@perches.com> wrote:
>
> 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...

The command I use is in the file, I re-run it every once in a while.
Ideally we could run this somehow automatically every -rc (for
instance), e.g. Linus could have it in his release script or something
like that, or maybe at the end of the merge window.

Even being more idealistic, clang-format could somehow do this itself
keeping a cache somewhere.

Cheers,
Miguel

  reply	other threads:[~2019-09-05  0:06 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
2019-09-05  0:05   ` Miguel Ojeda [this message]
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=CANiq72nVtTa17pnOhKKjx6NY3eYjU5FcXcN4MxFJkwkwV3+ghQ@mail.gmail.com \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.