From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: git@vger.kernel.org
Subject: Re: gitignore excludes too much
Date: Tue, 13 Jan 2009 18:36:24 +0100 [thread overview]
Message-ID: <496CD118.7000302@drmicha.warpmail.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0901131429020.23531@fbirervta.pbzchgretzou.qr>
Jan Engelhardt venit, vidit, dixit 01/13/09 14:30:
> Hi,
>
>
> I noticed that having "*.d" in .gitignore ignores files that would start
> with a dot, such as ".main.o.d". This is against Unix shell behavior;
> but maybe it's a feature rather than a bug?
> In case of latter, please fix :-)
git uses fnmatch with the last option (flags) being either 0 (for most
purposes) or FNM_PATHNAME (leading /), but never with FNM_PERIOD.
Think "sh with dotglob set" ;)
Since dotfiles tend to be the ones which are not tracked this behaviour
is the more practical one (compared to using FNM_PERIOD and forcing the
typical user to write two patterns).
Cheers,
Michael
prev parent reply other threads:[~2009-01-13 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 13:30 gitignore excludes too much Jan Engelhardt
2009-01-13 17:36 ` Michael J Gruber [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=496CD118.7000302@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=jengelh@medozas.de \
/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).