All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Desaulniers <ndesaulniers@google.com>
To: Toru Komatsu <k0ma@utam0k.jp>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	Tom Roeder <tmroeder@google.com>
Subject: Re: [PATCH] .gitignore: Add compilation database files
Date: Mon, 22 Jul 2019 12:25:05 -0700	[thread overview]
Message-ID: <CAKwvOdmRPGAbq29peHXrryqqYzc+6-Ag7+GDr7kYLQihQ0fHuw@mail.gmail.com> (raw)
In-Reply-To: <20190721085409.24499-1-k0ma@utam0k.jp>

On Sun, Jul 21, 2019 at 1:54 AM Toru Komatsu <k0ma@utam0k.jp> wrote:
>
> This file is used by clangd to use language server protocol.
> It can be generated at each compile using scripts/gen_compile_commands.py.
> Therefore it is different depending on the environment and should be
> ignored.
>
> Signed-off-by: Toru Komatsu <k0ma@utam0k.jp>
> ---
>  .gitignore | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/.gitignore b/.gitignore
> index 8f5422cba6e2..025d887f64f1 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -142,3 +142,6 @@ x509.genkey
>
>  # Kdevelop4
>  *.kdev4
> +
> +# Clang's compilation database files
> +/compile_commands.json

Thanks for the patch!
Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
Also, if you're doing anything exciting with compile_commands.json,
I'd love to know.  We're using it for static analyses.

-- 
Thanks,
~Nick Desaulniers

  reply	other threads:[~2019-07-22 19:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-21  8:54 [PATCH] .gitignore: Add compilation database files Toru Komatsu
2019-07-22 19:25 ` Nick Desaulniers [this message]
2019-07-23 15:33 ` Masahiro Yamada
2019-07-23 16:28   ` Toru Komatsu
2019-07-23 16:36     ` Masahiro Yamada
2019-07-23 19:46     ` 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=CAKwvOdmRPGAbq29peHXrryqqYzc+6-Ag7+GDr7kYLQihQ0fHuw@mail.gmail.com \
    --to=ndesaulniers@google.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=k0ma@utam0k.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tmroeder@google.com \
    --cc=yamada.masahiro@socionext.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 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.