[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKwvOdnEbFdOJj2BVsfN75OAVJYgo3hAj1ceXRRC6r0pwNtqnw@mail.gmail.com>
Date: Wed, 19 Jun 2019 12:53:48 -0700
From: Nick Desaulniers <ndesaulniers@...gle.com>
To: Joe Perches <joe@...ches.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
clang-built-linux <clang-built-linux@...glegroups.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: add CLANG/LLVM BUILD SUPPORT info
On Wed, Jun 19, 2019 at 11:27 AM Joe Perches <joe@...ches.com> wrote:
>
> On Wed, 2019-06-19 at 11:18 -0700, Nick Desaulniers wrote:
> > Add keyword support so that our mailing list gets cc'ed for clang/llvm
> > patches.
>
> You'd also possibly get cc'd on patches that merely mention
> clang or llvm like any change to clang-format. It could be
> many files that aren't interesting.
>
> $ git grep -i -w -P --name-only '(?i:clang|llvm)' | wc -l
> 134
That's very much intentional. We currently get ~11 emails a day from
various CI services (KernelCI, 0day bot), patch authors, etc. so I
don't think this adds too much more and it's mostly signal (signal to
noise). Maybe the bpf stuff would be less relevant, but I don't think
it hurts.
> Please use a single tab after each : like below
gah! My editor does flag this
(https://github.com/nickdesaulniers/dotfiles/blob/37359525f5a403b4ed2d3f9d1bbbee2da8ec8115/.vimrc#L35-L41)
whether or not I notice is sadly another story. Good catch, v2
inbound.
--
Thanks,
~Nick Desaulniers
Powered by blists - more mailing lists