git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: <git@vger.kernel.org>, Taylor Blau <me@ttaylorr.com>
Subject: Re: [PATCH] gitignore: ignore clangd .cache directory
Date: Fri, 04 Aug 2023 10:56:31 -0700	[thread overview]
Message-ID: <xmqqwmya1yk0.fsf@gitster.g> (raw)
In-Reply-To: <20230804171328.1737188-1-sandals@crustytoothpaste.net> (brian m. carlson's message of "Fri, 4 Aug 2023 17:13:28 +0000")

"brian m. carlson" <sandals@crustytoothpaste.net> writes:

> From: "brian m. carlson" <bk2204@github.com>
>
> In at least some versions of clangd, including version 15 in Ubuntu
> 23.04, a directory, .cache, is written in the root of the repository
> with index information about the files in the repository.  Since clangd
> is the most common language server protocol (LSP) implementation for C,
> and we already support it using the GENERATE_COMPILATION_DATABASE flags
> to make it functional, it's likely many users are using or will want to
> use it.
>
> As a result, ignore the ".cache" directory to help avoid users
> accidentally committing the data.

Thanks.  Let's fork from maint and queue it directly on 'next', and
fast track it to the upcoming release.

> Signed-off-by: brian m. carlson <bk2204@github.com>
> ---
>  .gitignore | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/.gitignore b/.gitignore
> index e875c59054..5e56e471b3 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -222,6 +222,7 @@
>  /TAGS
>  /cscope*
>  /compile_commands.json
> +/.cache/
>  *.hcc
>  *.obj
>  *.lib

      reply	other threads:[~2023-08-04 17:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 17:13 [PATCH] gitignore: ignore clangd .cache directory brian m. carlson
2023-08-04 17:56 ` Junio C Hamano [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=xmqqwmya1yk0.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.com \
    --cc=sandals@crustytoothpaste.net \
    /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;
as well as URLs for NNTP newsgroup(s).