[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72nVtTa17pnOhKKjx6NY3eYjU5FcXcN4MxFJkwkwV3+ghQ@mail.gmail.com>
Date: Thu, 5 Sep 2019 02:05:49 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Joe Perches <joe@...ches.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] clang-format for v5.3-rc8
On Thu, Sep 5, 2019 at 1:35 AM Joe Perches <joe@...ches.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
Powered by blists - more mailing lists