From: WANG Xuerui <kernel@xen0n.name>
To: Song Liu <song@kernel.org>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
WANG Xuerui <git@xen0n.name>
Subject: [PATCH 4/5] raid6: test: make sure all intermediate and artifact files are .gitignored
Date: Mon, 31 Jul 2023 18:49:10 +0800 [thread overview]
Message-ID: <20230731104911.411964-5-kernel@xen0n.name> (raw)
In-Reply-To: <20230731104911.411964-1-kernel@xen0n.name>
From: WANG Xuerui <git@xen0n.name>
Currently when the raid6test utility is built, the resulting binary and
an int.uc file are not being ignored, which can get inadvertently
committed as a result when one works on the raid6 code. Ignore them to
make `git status` clean at all times.
Signed-off-by: WANG Xuerui <git@xen0n.name>
---
lib/raid6/test/.gitignore | 2 ++
1 file changed, 2 insertions(+)
create mode 100644 lib/raid6/test/.gitignore
diff --git a/lib/raid6/test/.gitignore b/lib/raid6/test/.gitignore
new file mode 100644
index 0000000000000..bb92e11396c6e
--- /dev/null
+++ b/lib/raid6/test/.gitignore
@@ -0,0 +1,2 @@
+/int.uc
+/raid6test
--
2.40.0
next prev parent reply other threads:[~2023-07-31 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 10:49 [PATCH 0/5] raid6: raid6test build fixes and cleanups WANG Xuerui
2023-07-31 10:49 ` [PATCH 1/5] raid6: remove the <linux/export.h> include from recov.c WANG Xuerui
2023-07-31 10:49 ` [PATCH 2/5] raid6: guard the tables.c include of <linux/export.h> with __KERNEL__ WANG Xuerui
2023-07-31 10:49 ` [PATCH 3/5] raid6: test: cosmetic cleanups for the test Makefile WANG Xuerui
2023-07-31 10:49 ` WANG Xuerui [this message]
2023-08-13 17:21 ` [PATCH 4/5] raid6: test: make sure all intermediate and artifact files are .gitignored Song Liu
2023-07-31 10:49 ` [PATCH 5/5] raid6: test: only check for Altivec if building on powerpc hosts WANG Xuerui
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=20230731104911.411964-5-kernel@xen0n.name \
--to=kernel@xen0n.name \
--cc=git@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=song@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;
as well as URLs for NNTP newsgroup(s).