From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, Eric Blake <eblake@redhat.com>,
Johannes Sixt <j6t@kdbg.org>, "Y.G." <yamomo1@hotmail.com>,
Eli Barzilay <eli@barzilay.org>
Subject: Re: [PATCH 3/4] Documentation: unanchored gitignore patterns match basename
Date: Mon, 7 Nov 2011 17:18:15 +0700 [thread overview]
Message-ID: <CACsJy8BLmanoWmUwT4uD+qosxbQYRCaACDFriLA6J7-jUztG6Q@mail.gmail.com> (raw)
In-Reply-To: <20111107080926.GC30486@elie.hsd1.il.comcast.net>
2011/11/7 Jonathan Nieder <jrnieder@gmail.com>:
> The rule described by v1.7.1.1~31^2 (gitignore.5: Clarify matching
> rules, 2010-03-05) is just false: simple gitignore patterns without a
> slash like "foo" and "cscope*" have always matched files in all
> directories, not just the toplevel, and a question mark cannot be used
> to match the slash separating path components.
>
> For example:
>
> foo/ - matches directories named "foo" throughout the tree
> Documentation?foo - does not match Documentation/foo
>
> Reported-by: Y.G. <yamomo1@hotmail.com>
> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Acked-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
--
Duy
next prev parent reply other threads:[~2011-11-07 10:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 8:04 [RFC/PATCH 0/5] gitignore.5 clarifications Jonathan Nieder
2011-11-07 8:07 ` [PATCH 1/4] Documentation/gitignore: "foo/" patterns match directories, not files under them Jonathan Nieder
2011-11-07 9:57 ` Nguyen Thai Ngoc Duy
2011-11-07 16:53 ` Junio C Hamano
2011-11-07 8:08 ` [PATCH 2/4] Documentation: clarify effect of '/' in gitignore(5) patterns Jonathan Nieder
2011-11-07 10:05 ` Nguyen Thai Ngoc Duy
2011-11-07 8:09 ` [PATCH 3/4] Documentation: unanchored gitignore patterns match basename Jonathan Nieder
2011-11-07 10:18 ` Nguyen Thai Ngoc Duy [this message]
2011-11-07 8:11 ` [PATCH 4/4] Documentation/gitignore: explain how to un-ignore part of a directory Jonathan Nieder
2011-11-07 10:23 ` Nguyen Thai Ngoc Duy
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=CACsJy8BLmanoWmUwT4uD+qosxbQYRCaACDFriLA6J7-jUztG6Q@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=eblake@redhat.com \
--cc=eli@barzilay.org \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=jrnieder@gmail.com \
--cc=yamomo1@hotmail.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).