linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yordan Karadzhov <y.karadz@gmail.com>
To: Mircea Cirjaliu <mircea.cirjaliu@yahoo.com>,
	linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] kernelshark: add .gitignore for generated/build files
Date: Mon, 27 Oct 2025 22:01:35 +0200	[thread overview]
Message-ID: <67b3a43c-8d6d-b1e0-de72-d7d7127bdbd2@gmail.com> (raw)
In-Reply-To: <ed24336c-4e14-48f5-ab0d-cd5f6f3f5c01@yahoo.com>

Hi Mircea,

On 10/24/25 23:01, Mircea Cirjaliu wrote:
> Not having a .gitignore will bloat git listings.
> Created a .gitignore for all build artifacts.
> 
> Signed-off-by: Mircea Cirjaliu <mircea.cirjaliu@yahoo.com>
> ---
>   .gitignore | 16 ++++++++++++++++
>   1 file changed, 16 insertions(+)
>   create mode 100644 .gitignore
> 
> diff --git a/.gitignore b/.gitignore
> new file mode 100644
> index 0000000..38a45ac
> --- /dev/null
> +++ b/.gitignore
> @@ -0,0 +1,16 @@
> +.vscode/
> +build/.cmake/
> +build/.qt/
> +build/CMakeCache.txt

There are files that are missing from the list here.
I guess this is because you are missing some of the
optional dependencies.
Please add also:

build/CMakeDoxyfile.in
build/CMakeDoxygenDefaults.cmake
build/CTestTestfile.cmake
build/tests/

> +build/CMakeFiles/
> +build/Makefile
> +build/cmake_install.cmake
> +build/compile_commands.json
> +build/examples/
> +build/include/
> +build/src/
> +bin/
> +lib/

and this directory:

tests/

> +kernelshark.desktop
> +libkshark.pc
> +org.freedesktop.kshark-record.policy

Thanks,
Yordan

      reply	other threads:[~2025-10-27 20:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ed24336c-4e14-48f5-ab0d-cd5f6f3f5c01.ref@yahoo.com>
2025-10-24 20:01 ` [PATCH] kernelshark: add .gitignore for generated/build files Mircea Cirjaliu
2025-10-27 20:01   ` Yordan Karadzhov [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=67b3a43c-8d6d-b1e0-de72-d7d7127bdbd2@gmail.com \
    --to=y.karadz@gmail.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=mircea.cirjaliu@yahoo.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;
as well as URLs for NNTP newsgroup(s).