From: Joe Perches <joe@perches.com>
To: Nick Desaulniers <ndesaulniers@google.com>, akpm@linux-foundation.org
Cc: clang-built-linux@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add CLANG/LLVM BUILD SUPPORT info
Date: Wed, 19 Jun 2019 11:27:42 -0700 [thread overview]
Message-ID: <d4b42858366e50f92b133ceb6399e9f16a7cef88.camel@perches.com> (raw)
In-Reply-To: <20190619181844.57696-1-ndesaulniers@google.com>
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
> diff --git a/MAINTAINERS b/MAINTAINERS
[]
> @@ -3940,6 +3940,14 @@ M: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
> S: Maintained
> F: .clang-format
>
> +CLANG/LLVM BUILD SUPPORT
> +L: clang-built-linux@googlegroups.com
> +W: https://clangbuiltlinux.github.io/
> +B: https://github.com/ClangBuiltLinux/linux/issues
> +C: irc://chat.freenode.net/clangbuiltlinux
> +S: Supported
> +K: \b(?i:clang|llvm)\b
> +
Please use a single tab after each : like below
CLANG/LLVM BUILD SUPPORT
L: clang-built-linux@googlegroups.com
W: https://clangbuiltlinux.github.io/
B: https://github.com/ClangBuiltLinux/linux/issues
C: irc://chat.freenode.net/clangbuiltlinux
S: Supported
K: \b(?i:clang|llvm)\b
next prev parent reply other threads:[~2019-06-19 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 18:18 Nick Desaulniers
2019-06-19 18:27 ` Joe Perches [this message]
2019-06-19 19:53 ` Nick Desaulniers
2019-06-20 0:19 ` [PATCH v2] " Nick Desaulniers
2019-06-20 2:54 ` Nathan Chancellor
2019-06-19 19:16 ` [PATCH] " Louis Taylor
2019-06-19 19:50 ` Nick Desaulniers
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=d4b42858366e50f92b133ceb6399e9f16a7cef88.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®