From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2] btrfs-progs: gitignore: Ignore hidden files
Date: Thu, 28 Feb 2019 10:22:06 +0800 [thread overview]
Message-ID: <20190228022206.16356-1-wqu@suse.com> (raw)
A lot of editor/IDE related config files are dotfiles, like .vimrc
or .clang_complete.
Instead of adding gitignore entry for each editor/IDE, just ignore all
dotfiles.
Signed-off-by: Qu Wenruo <wqu@suse.com>
---
changelog
v2:
- Change "hidden files" to "dotfiles" in the commit message.
- No longer mention the kernel gitignore behavior in the commit message.
---
.gitignore | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.gitignore b/.gitignore
index d9f022c48c7d..aadf9ae77d41 100644
--- a/.gitignore
+++ b/.gitignore
@@ -64,7 +64,7 @@
/cscope.files
/cscope.in.out
/cscope.po.out
-.clang_complete
+.*
/Documentation/Makefile
/Documentation/*.html
--
2.21.0
next reply other threads:[~2019-02-28 2:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 2:22 Qu Wenruo [this message]
2019-03-05 12:27 ` [PATCH v2] btrfs-progs: gitignore: Ignore hidden files David Sterba
2019-03-05 12:35 ` Qu Wenruo
2019-03-05 13:37 ` David Sterba
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=20190228022206.16356-1-wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.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).