Re: bug: sparse config interpretation incorrectness in 2.8.0-rc2

From: Duy Nguyen <pclouds@gmail.com>
Date: Mar 17, 2016, 14:00 UTC
Message-ID: <CACsJy8D1e5zd-b6CsszHGcNjMPedyZSrZpqdWeCUGdMD5UP7qQ@mail.gmail.com>
In-Reply-To: <alpine.DEB.2.20.1603171444210.4690@virtualbox>

On Thu, Mar 17, 2016 at 8:46 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 7 quoted lines

> Unfortunately, this does not help me at all. In the use case I am trying
> to get to work fast, we have tons and tons of directories and need *one*
> file in pretty much *all* of those directories, and exclude most of the
> other files.
>
> To make matters even worse, the list of excluded (or included) files is
> constantly changing.

OK very weird use case to me :) There's something you might try. [1] can help trimming unrelated patterns, fewer patterns to match for a dir, faster matching.

I knew it might help speed up sparse checkout (because we can't spread sparse patterns over many .gitignore files, we only have one place for all patterns). I did try at some point. I just don't remember if I gave up because I didn't think it's worth the effort or I found out something wrong with it for sparse checkout case. It may or may help your case, depending on the patterns, of course.

[1] http://article.gmane.org/gmane.comp.version-control.git/217958

-- 
Duy