From: Maaartin <grajcar1@seznam.cz>
To: git@vger.kernel.org
Subject: Re: [PROPOSAL] .gitignore syntax modification
Date: Mon, 11 Oct 2010 23:46:28 +0000 (UTC) [thread overview]
Message-ID: <loom.20101012T013931-754@post.gmane.org> (raw)
In-Reply-To: FD4E6D0A-34E6-4FC4-AA7A-327E07AB58D4@sb.org
Kevin Ballard <kevin <at> sb.org> writes:
> On Oct 8, 2010, at 2:58 PM, Maaartin wrote:
> That's not the right layout. I'd have to do
>
> *.xcodeproj/*
> !*.xcodeproj/project.pbxproj
> */*.xcodeproj/*
> !*/*.xcodeproj/project.pbxproj
>
> And so on, once for each possible level of nesting.
Sorry, that's was I meant, I was too sloppy/tired/stupid when writing this.
> ... The problem I'm talking about is
> simply that you cannot write a pattern that includes a slash and have that
pattern match at any nesting level.
I see I wrong again. At least I learned something.
> Upon further reflection, if we stick with platform-provided fnmatch() we
don't have to special-case a
> prefixed **/. We could simply define patterns as always matching in that way,
and you can use the
> already-existing prefixed / to root it at the current level. So if my pattern
looks like
>
> *.xcodeproj/*
>
> Then it will attempt to match this pattern against the last 2 path components
of any path rooted in this
> directory. It can simply count the slashes to determine the number of path
components. If I really want it
> to just match *.xcodeproj files in the current directory then my pattern
should look like
>
> /*.xcodeproj/*
IMHO, this is how it should work, simple and consequent. Sorry for clobbering
this thread by my mistakes.
next prev parent reply other threads:[~2010-10-11 23:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 21:26 [PROPOSAL] .gitignore syntax modification Kevin Ballard
2010-10-08 21:58 ` Maaartin
2010-10-09 0:03 ` Kevin Ballard
2010-10-11 23:46 ` Maaartin [this message]
2010-10-13 2:24 ` Nguyen Thai Ngoc Duy
2010-10-13 2:32 ` Kevin Ballard
2010-10-13 2:40 ` Jonathan Nieder
2010-10-13 3:05 ` Kevin Ballard
2010-10-13 16:51 ` Junio C Hamano
2010-10-13 12:15 ` Nguyen Thai Ngoc Duy
2010-10-15 11:01 ` Kevin Ballard
2010-10-15 12:57 ` Nguyen Thai Ngoc Duy
2010-10-15 20:15 ` Kevin Ballard
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20101012T013931-754@post.gmane.org \
--to=grajcar1@seznam.cz \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).