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

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Mar 18, 2016, 15:49 UTC
Message-ID: <alpine.DEB.2.20.1603181647160.4690@virtualbox>
In-Reply-To: <CACsJy8D1e5zd-b6CsszHGcNjMPedyZSrZpqdWeCUGdMD5UP7qQ@mail.gmail.com>

Hi Duy,

On Thu, 17 Mar 2016, Duy Nguyen wrote:

Show 13 quoted lines

> On Thu, Mar 17, 2016 at 8:46 PM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
> > 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.

Sadly, [1] (exclude: filter out patterns not applicable to the current directory) would not help at all, because the regular use case really would use the top-level directory as current one.

So I really need to speed up the sparse machinery from O(m*n) (where m is the number of entries in the sparse-checkout file and n is the number of files in the index).

Ciao, Dscho