All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Jensen <jjensen@workspacewhiz.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>,
	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 11:51:51 -0600	[thread overview]
Message-ID: <506C7B37.3080804@workspacewhiz.com> (raw)
In-Reply-To: <CACsJy8DRxbjcRpbO30vOCo9D+TK_dDX_oiocZSOtnGAR2jAOFw@mail.gmail.com>

----- Original Message -----
From: Nguyen Thai Ngoc Duy
Date: 10/3/2012 7:42 AM
> On Wed, Oct 3, 2012 at 8:35 PM, Jens Lehmann <Jens.Lehmann@web.de> wrote:
>> */foo/bar
>> */*/foo/bar
>> */*/*/foo/bar
>>
>> Using "**/foo/bar" instead would be a great improvement
> If this "**/foo/bar" (i.e. no wildcards except one ** at the
> beginning) is popular, we could optimize this case, turning fmatch()
> into strncmp(), just like what we do for "foobar*"
FWIW, I would like to see this in .gitattributes as well.  I have a 
version of .gitattributes that supports recursive wildcards that I use 
for specifying filters.

-Josh

  parent reply	other threads:[~2012-10-03 17:53 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
2012-10-03 13:42         ` Nguyen Thai Ngoc Duy
2012-10-03 13:51           ` Jens Lehmann
2012-10-03 17:51           ` Joshua Jensen [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=506C7B37.3080804@workspacewhiz.com \
    --to=jjensen@workspacewhiz.com \
    --cc=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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.