From: Mike Fleetwood <mike.fleetwood@googlemail.com>
To: Stefan Traby <stefan@hello-penguin.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>, Qu Wenruo <wqu@suse.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs-progs: gitignore: Ignore hidden files
Date: Wed, 27 Feb 2019 13:58:18 +0000 [thread overview]
Message-ID: <CAMU1PDh=Q0uyOOmg63UNs597DY01+AmAkDayDKRsa1HrsBPFTQ@mail.gmail.com> (raw)
In-Reply-To: <20190227114359.GA28913@hello-penguin.com>
On Wed, 27 Feb 2019 at 11:44, Stefan Traby <stefan@hello-penguin.com> wrote:
>
> On Wed, Feb 27, 2019 at 07:29:13PM +0800, Qu Wenruo wrote:
> > On 2019/2/27 下午7:22, Mike Fleetwood wrote:
> > > On Wed, 27 Feb 2019 at 05:16, Qu Wenruo <wqu@suse.com> wrote:
> > >>
> > >> A lot of editor/IDE related config files are hidden files, like .vimrc
> > >> or .clang_complete.
> > >>
> > >> Instead of adding gitignore entry for each editor/IDE, just ignore all
> > >> hidden files like what kernel does.
> > > I think you mean:
> > > files starting with ".", like ls does by default without the -a flag.
> >
> > When I punched the words "linux hidden file" into google, I got quite a
> > lot of pages showing 'In the Linux operating system, a hidden file is
> > any file that begins with a "."'
> >
> > So I think the words "hidden files" should be more or less OK?
My main point was that you said "hidden files like what kernel does"
which is not true.
>
> I think the word "dotfiles" is ok.
Shortening to "just ignore all dotfiles" would be a good choice.
prev parent reply other threads:[~2019-02-27 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 5:16 [PATCH] btrfs-progs: gitignore: Ignore hidden files Qu Wenruo
2019-02-27 11:22 ` Mike Fleetwood
2019-02-27 11:29 ` Qu Wenruo
2019-02-27 11:43 ` Stefan Traby
2019-02-27 13:58 ` Mike Fleetwood [this message]
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='CAMU1PDh=Q0uyOOmg63UNs597DY01+AmAkDayDKRsa1HrsBPFTQ@mail.gmail.com' \
--to=mike.fleetwood@googlemail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=stefan@hello-penguin.com \
--cc=wqu@suse.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).