public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Jan Polensky" <japo@linux.ibm.com>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v2] Add cglangd specific files to gitignore
Date: Wed, 25 Mar 2026 15:34:16 +0000	[thread overview]
Message-ID: <69c40079.df0a0220.1260e7.732d@mx.google.com> (raw)
In-Reply-To: <acP66MTKk3LzceQD@li-276bd24c-2dcc-11b2-a85c-945b6f05615c.ibm.com>

> Small nit: with the leading '/', /compile_commands.json only matches in the
> repository root. However compile_commands.json is often generated in
> build/subdirectories (depending on where the build is run). If the goal is to
> prevent accidental inclusion anywhere, the pattern should be unanchored, e.g.:
> 
>   compile_commands.json
> 
> (or equivalently **/compile_commands.json).
> 
> I can reproduce this by generating it from a subdir (e.g. via bear), which
> produces ./compile_commands.json there.
> 
> 	bear -- make
> 
> Thanks,
> Jan

I see, I never used bear honestly, so this might be a bit tricky for me.
But I see the value and the correlation with clangd, so we can safely add

**/compile_commands.json

Will send an another patch.

Regards,
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2026-03-25 15:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 10:51 [LTP] [PATCH v2] Add cglangd specific files to gitignore Andrea Cervesato
2026-03-25 15:10 ` Jan Polensky
2026-03-25 15:34   ` Andrea Cervesato via ltp [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=69c40079.df0a0220.1260e7.732d@mx.google.com \
    --to=ltp@lists.linux.it \
    --cc=andrea.cervesato@suse.com \
    --cc=japo@linux.ibm.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