From: Willy Tarreau <w@1wt.eu>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
"Fernanda Ma'rouf" <fernandafmr12@gnuweeb.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH nolibc v1] selftests/nolibc: Avoid generated files being committed
Date: Wed, 20 Jul 2022 05:37:45 +0200 [thread overview]
Message-ID: <20220720033745.GC3106@1wt.eu> (raw)
From: "Fernanda Ma'rouf" <fernandafmr12@gnuweeb.org>
After running the nolibc tests, the "git status" is not clean because
the generated files are not ignored. Create a `.gitignore` inside the
selftests/nolibc directory to ignore them.
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Cc: Fernanda Ma'rouf <fernandafmr2@gmail.com>
Signed-off-by: Fernanda Ma'rouf <fernandafmr12@gnuweeb.org>
Signed-off-by: Willy Tarreau <w@1wt.eu>
---
Paul,
Fernanda sent me this which I think is a desirable cleanup to the
series I sent you. If you're fine with adding it on top of what you
already have, that's great. Otherwise I can queue it here for next
time, but this should improve the user's experience.
Thanks,
Willy
--
tools/testing/selftests/nolibc/.gitignore | 4 ++++
1 file changed, 4 insertions(+)
create mode 100644 tools/testing/selftests/nolibc/.gitignore
diff --git a/tools/testing/selftests/nolibc/.gitignore b/tools/testing/selftests/nolibc/.gitignore
new file mode 100644
index 000000000000..4696df589d68
--- /dev/null
+++ b/tools/testing/selftests/nolibc/.gitignore
@@ -0,0 +1,4 @@
+/initramfs/
+/nolibc-test
+/run.out
+/sysroot/
base-commit: 1e93ece89dd1c6217b92ef6fc100df9ba202c30c
next reply other threads:[~2022-07-20 3:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 3:37 Willy Tarreau [this message]
2022-07-20 3:59 ` [PATCH nolibc v1] selftests/nolibc: Avoid generated files being committed Paul E. McKenney
2022-07-20 4:54 ` Willy Tarreau
-- strict thread matches above, loose matches on Subject: below --
2022-07-19 10:56 Fernanda Ma'rouf
2022-07-20 3:30 ` Willy Tarreau
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=20220720033745.GC3106@1wt.eu \
--to=w@1wt.eu \
--cc=ammarfaizi2@gnuweeb.org \
--cc=fernandafmr12@gnuweeb.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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