From: cel@kernel.org
To: amir73il@gmail.com, krisman@collabora.com
Cc: gregkh@linuxfoundation.org, jack@suse.cz, sashal@kernel.org,
stable@vger.kernel.org, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org, tytso@mit.edu,
alexey.makhalov@broadcom.com, vasavi.sirnapalli@broadcom.com,
florian.fainelli@broadcom.com,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: [PATCH v5.10.y 3/3] Add gitignore file for samples/fanotify/ subdirectory
Date: Thu, 25 Jul 2024 11:32:29 -0400 [thread overview]
Message-ID: <20240725153229.13407-4-cel@kernel.org> (raw)
In-Reply-To: <20240725153229.13407-1-cel@kernel.org>
From: Linus Torvalds <torvalds@linux-foundation.org>
[ Upstream commit c107fb9b4f8338375b3e865c3d2c1d98ccb3a95a ]
Commit 5451093081db ("samples: Add fs error monitoring example") added a
new sample program, but didn't teach git to ignore the new generated
files, causing unnecessary noise from 'git status' after a full build.
Add the 'fs-monitor' sample executable to the .gitignore for this
subdirectory to silence it all again.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
samples/fanotify/.gitignore | 1 +
1 file changed, 1 insertion(+)
create mode 100644 samples/fanotify/.gitignore
diff --git a/samples/fanotify/.gitignore b/samples/fanotify/.gitignore
new file mode 100644
index 000000000000..d74593e8b2de
--- /dev/null
+++ b/samples/fanotify/.gitignore
@@ -0,0 +1 @@
+fs-monitor
--
2.45.2
next prev parent reply other threads:[~2024-07-25 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 15:32 [PATCH v5.10.y 0/3] Apply fanotify-related documentation changes cel
2024-07-25 15:32 ` [PATCH v5.10.y 1/3] samples: Add fs error monitoring example cel
2024-07-25 15:32 ` [PATCH v5.10.y 2/3] samples: Make fs-monitor depend on libc and headers cel
2024-07-25 15:32 ` cel [this message]
2024-08-13 10:30 ` [PATCH v5.10.y 0/3] Apply fanotify-related documentation changes Greg KH
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=20240725153229.13407-4-cel@kernel.org \
--to=cel@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=alexey.makhalov@broadcom.com \
--cc=amir73il@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=krisman@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=vasavi.sirnapalli@broadcom.com \
/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).