mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: linux-kernel@vger.kernel.org, masahiroy@kernel.org,
	ojeda@kernel.org,  Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, kernel-team@meta.com,
	linux-pm@vger.kernel.org,  Eduard Zingerman <eddyz87@gmail.com>
Subject: Re: [PATCH v2] .gitignore: ignore compile_commands.json globally
Date: Tue, 12 Aug 2025 16:00:04 -0700	[thread overview]
Message-ID: <175503960408.1315825.6402987041334486305.b4-ty@kernel.org> (raw)
In-Reply-To: <20250606214840.3165754-1-andrii@kernel.org>


On Fri, 06 Jun 2025 14:48:40 -0700, Andrii Nakryiko wrote:
> compile_commands.json can be used with clangd to enable language server
> protocol-based assistance. For kernel itself this can be built with
> scripts/gen_compile_commands.py, but other projects (e.g., libbpf, or
> BPF selftests) can benefit from their own compilation database file,
> which can be generated successfully using external tools, like bear [0].
> 
> So, instead of adding compile_commands.json to .gitignore in respective
> individual projects, let's just ignore it globally anywhere in Linux repo.
> 
> [...]

Applied, thanks!

[1/1] .gitignore: ignore compile_commands.json globally
      https://git.kernel.org/kbuild/c/f7cc3caea0005

Best regards,
-- 
Nathan Chancellor <nathan@kernel.org>


      parent reply	other threads:[~2025-08-12 23:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-06 21:48 Andrii Nakryiko
2025-06-07  9:27 ` Miguel Ojeda
2025-06-12 20:28   ` Andrii Nakryiko
2025-08-12 21:55     ` Andrii Nakryiko
2025-08-12 22:14       ` Nathan Chancellor
2025-08-12 22:22         ` Andrii Nakryiko
2025-08-12 23:00 ` Nathan Chancellor [this message]

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=175503960408.1315825.6402987041334486305.b4-ty@kernel.org \
    --to=nathan@kernel.org \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=ojeda@kernel.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 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®