From: Jens Lehmann <Jens.Lehmann@web.de>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
Stefano Lattarini <stefano.lattarini@gmail.com>,
Git List <git@vger.kernel.org>
Subject: Re: [ENHANCEMENT] Allow '**' pattern in .gitignore
Date: Wed, 03 Oct 2012 15:35:31 +0200 [thread overview]
Message-ID: <506C3F23.9000009@web.de> (raw)
In-Reply-To: <CACsJy8CUK0g4FhuJxzJqN7qS2apoO2zYdg_SGvWzEN5dGcHhaA@mail.gmail.com>
Am 03.10.2012 13:35, schrieb Nguyen Thai Ngoc Duy:
> On Tue, Oct 2, 2012 at 3:24 PM, Ramkumar Ramachandra <artagnon@gmail.com> wrote:
>> Stefano Lattarini wrote:
>>> On 10/02/2012 09:21 AM, Ramkumar Ramachandra wrote:
>>>> Hi,
>>>>
>>>> I've often found the '**' (extended) shell glob useful for matching
>>>> any string crossing directory boundaries: it's especially useful if
>>>> you only have a toplevel .gitignore, as opposed to a per-directory
>>>> .gitignore. Unfortunately, .gitignore currently uses fnmatch(3), and
>>>> doesn't recognize '**'. Would extending the .gitignore format to
>>>> accept this be a useful feature? Would it involve re-implementing and
>>>> extending fnmatch, or is there some other way?
>>>>
>>> I think there is a topic in flight about this:
>>>
>>> <http://thread.gmane.org/gmane.comp.version-control.git/206406>
>
> While I'm behind this series, I have no use cases for it in my
> repositories. It's tested in git test suite but that's about it. Some
> feedback would be nice, especially on the performance side if you do a
> lot of ignores.
I really like it as we do have use cases at my dayjob. Due to our
naming conventions in subdirectories we have stuff like this in our
.gitignore files:
*/foo/bar
*/*/foo/bar
*/*/*/foo/bar
Using "**/foo/bar" instead would be a great improvement (I looked
into adding that myself some time ago, but decided it wasn't a low
hanging fruit).
Maybe I'll find time do do some performance measurements until the
weekend, what numbers are you interested in? Will a hot cache "time
git status" be sufficient or are you interested in other numbers too?
next prev parent reply other threads:[~2012-10-03 13:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 7:21 [ENHANCEMENT] Allow '**' pattern in .gitignore Ramkumar Ramachandra
2012-10-02 7:58 ` Stefano Lattarini
2012-10-02 8:24 ` Ramkumar Ramachandra
2012-10-03 11:35 ` Nguyen Thai Ngoc Duy
2012-10-03 13:35 ` Jens Lehmann [this message]
2012-10-03 13:42 ` Nguyen Thai Ngoc Duy
2012-10-03 13:51 ` Jens Lehmann
2012-10-03 17:51 ` Joshua Jensen
2012-10-04 1:34 ` 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
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=506C3F23.9000009@web.de \
--to=jens.lehmann@web.de \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=stefano.lattarini@gmail.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.
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).