From: Johannes Sixt <j.sixt@viscovery.net>
To: Eli Barzilay <eli@barzilay.org>
Cc: git@vger.kernel.org
Subject: Re: `*' gitignores and nested ignores
Date: Fri, 25 Mar 2011 09:18:23 +0100 [thread overview]
Message-ID: <4D8C4FCF.5060900@viscovery.net> (raw)
In-Reply-To: <19851.6264.179471.935771@winooski.ccs.neu.edu>
Am 3/24/2011 11:10, schrieb Eli Barzilay:
> According to the man page, a .gitignore file that is deeper has higher
> precedence, and a `!' line overrides lower precedence ignores. I
> tried that, and it works in cases like the last "vmlinux*" example.
>
> But it doesn't work if the lower precedence directory has a "*"
> pattern. If the last example from the man page is changed to:
>
> $ cat .gitignore
> *
> $ ls arch/foo/kernel/vm*
> arch/foo/kernel/vmlinux.lds.S
> $ echo ´!/vmlinux*´ >arch/foo/kernel/.gitignore
>
> then -- IIUC -- the second ignore should work the same, but it
> doesn't. This also happens if the first pattern is "/*".
>
> Is this a bug?
This has been discussed before, and IMNSHO, this is not a bug:
http://thread.gmane.org/gmane.comp.version-control.git/157190
-- Hannes
next prev parent reply other threads:[~2011-03-25 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 10:10 `*' gitignores and nested ignores Eli Barzilay
2011-03-25 8:18 ` Johannes Sixt [this message]
2011-03-25 9:37 ` Eli Barzilay
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=4D8C4FCF.5060900@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=eli@barzilay.org \
--cc=git@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).