From: Willy Tarreau <[email protected]>
To: "Fernanda Ma'rouf" <[email protected]>
Cc: Ammar Faizi <[email protected]>,
Linux Kernel Mailing List <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
"Fernanda Ma'rouf" <[email protected]>
Subject: Re: [PATCH nolibc v1] selftests/nolibc: Avoid generated files being committed
Date: Wed, 20 Jul 2022 05:30:31 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Hi Fernanda,
On Tue, Jul 19, 2022 at 05:56:25PM +0700, Fernanda Ma'rouf wrote:
> 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.
Ah thank you, I didn't know that .gitignore was per-directory, I though
it was only at the top. Yes that's a nice improvement, I'll forward it
to Paul as it's reasonable and not too late I think.
Thanks,
Willy
next prev parent reply other threads:[~2022-07-20 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 10:56 [PATCH nolibc v1] selftests/nolibc: Avoid generated files being committed Fernanda Ma'rouf
2022-07-20 3:30 ` Willy Tarreau [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-19 10:50 Fernanda Ma'rouf
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] \
[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