From: Brandon Pollack <brpol@chromium.org>
To: linux-kernel@vger.kernel.org
Cc: masahiroy@kernel.org, ojeda@kernel.org, alex.gaynor@gmail.com,
keescook@chromium.org, nathan@kernel.org,
Brandon Pollack <brpol@chromium.org>
Subject: [PATCH] .gitignore: ignore smatch generated files
Date: Thu, 27 Apr 2023 02:33:45 +0000 [thread overview]
Message-ID: <20230427023345.1369433-1-brpol@chromium.org> (raw)
ignore smatch generated files.
Signed-off-by: Brandon Pollack <brpol@chromium.org>
---
New to development and looking for tasks to work on to get familiar with
code, I noticed smatch generates some files at the root. Since this
tool seems frequent for newbies like myself I thought it would be worth
getting rid of the chance of accidentally committing these files.
---
.gitignore | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/.gitignore b/.gitignore
index 70ec6037fa7a..04472c37b6df 100644
--- a/.gitignore
+++ b/.gitignore
@@ -173,3 +173,11 @@ sphinx_*/
# Rust analyzer configuration
/rust-project.json
+
+# Smatch tree outputs
+smatch_compile.warns
+smatch_db.sqlite
+smatch_warns.txt
+smatch_warns.txt.caller_info
+smatch_warns.txt.sql
+trinity_smatch.[ch]
--
2.40.1.495.gc816e09b53d-goog
next reply other threads:[~2023-04-27 2:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 2:33 Brandon Pollack [this message]
2023-04-27 7:54 ` Miguel Ojeda
2023-04-27 11:20 ` Dan Carpenter
2023-04-28 2:55 ` Brandon Ross Pollack
2023-05-02 15:24 ` Dan Carpenter
[not found] ` <CALWYx-ayGvg0iuRi15+JyGrThmiOqzwxPNfEfpqUpbsknkcpgg@mail.gmail.com>
2023-05-08 5:04 ` Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2023-04-26 3:46 Brandon Pollack
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=20230427023345.1369433-1-brpol@chromium.org \
--to=brpol@chromium.org \
--cc=alex.gaynor@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@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®