From: Ammar Faizi <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Ammar Faizi <[email protected]>,
io-uring Mailing List <[email protected]>,
GNU/Weeb Mailing List <[email protected]>
Subject: [PATCH liburing v1 0/2] SPDX fix and .gitignore improvement
Date: Sun, 3 Apr 2022 16:56:00 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Jens,
Two patches in this series. The first patch is SPDX-License-Identifier
fix. The second patch is a small improvement for .gitignore w.r.t. test.
When adding a new test, we often forget to add the new test binary to
`.gitignore`. Append `.test` to the test binary filename, this way we
can use a wildcard matching "test/*.test" in `.gitignore` to ignore all
test binary files.
Goals:
- Make the .gitignore simpler.
- Avoid the burden of adding a new test to .gitignore.
Signed-off-by: Ammar Faizi <[email protected]>
---
Ammar Faizi (2):
src/int_flags.h: Add missing SPDX-License-Identifier
test/Makefile: Append `.test` to the test binary filename
.gitignore | 132 +-----------------------------------------------
src/int_flags.h | 1 +
test/Makefile | 8 +--
3 files changed, 7 insertions(+), 134 deletions(-)
base-commit: 314dd7ba2aa9d0ba5bb9a6ab28b7204dd319e386
--
Ammar Faizi
next reply other threads:[~2022-04-03 9:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 9:56 Ammar Faizi [this message]
2022-04-03 9:56 ` [PATCH liburing v1 1/2] src/int_flags.h: Add missing SPDX-License-Identifier Ammar Faizi
2022-04-03 9:56 ` [PATCH liburing v1 2/2] test/Makefile: Append `.test` to the test binary filename Ammar Faizi
2022-04-03 14:51 ` Jens Axboe
2022-04-03 14:55 ` Ammar Faizi
2022-04-03 15:00 ` Jens Axboe
2022-04-03 15:05 ` Ammar Faizi
2022-04-03 15:06 ` Jens Axboe
2022-04-03 14:52 ` (subset) [PATCH liburing v1 0/2] SPDX fix and .gitignore improvement Jens Axboe
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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