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 v2] kernelshark: add .gitignore for generated/build files
Date: Thu, 30 Oct 2025 20:51:59 +0200	[thread overview]
Message-ID: <d435f036-a631-2c48-cec0-849d116d1fb6@gmail.com> (raw)
In-Reply-To: <7f44503b-2ae8-4ac1-8635-a5dd4d0b286f@yahoo.com>

The patch is applied. Thanks!

Yordan


On 10/28/25 21:08, 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 | 24 ++++++++++++++++++++++++
>   1 file changed, 24 insertions(+)
>   create mode 100644 .gitignore
> 
> diff --git a/.gitignore b/.gitignore
> new file mode 100644
> index 0000000..cbeb499
> --- /dev/null
> +++ b/.gitignore
> @@ -0,0 +1,24 @@
> +.vscode/
> +build/.cmake/
> +build/.qt/
> +build/CMakeCache.txt
> +build/CMakeFiles/
> +build/CMakeDoxyfile.in
> +build/CMakeDoxygenDefaults.cmake
> +build/CTestTestfile.cmake
> +build/Makefile
> +build/cmake_install.cmake
> +build/compile_commands.json
> +build/examples/
> +build/include/
> +build/src/
> +build/Testing/
> +build/tests/
> +bin/
> +lib/
> +tests/kshark-gui-tests
> +tests/kshark-tests
> +tests/*.so
> +kernelshark.desktop
> +libkshark.pc
> +org.freedesktop.kshark-record.policy

      reply	other threads:[~2025-10-30 18:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7f44503b-2ae8-4ac1-8635-a5dd4d0b286f.ref@yahoo.com>
2025-10-28 19:08 ` [PATCH v2] kernelshark: add .gitignore for generated/build files Mircea Cirjaliu
2025-10-30 18:51   ` 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=d435f036-a631-2c48-cec0-849d116d1fb6@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).