Re: ls-files --exclude broken?

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 15, 2010, 23:12 UTC
Message-ID: <7v62y661pl.fsf@alter.siamese.dyndns.org>
In-Reply-To: <AANLkTimuTHvA+qjqpmz=VkCpTTiRA7imb5+ZyTVmPwYy@mail.gmail.com>

Jay Soffian <jaysoffian@gmail.com> writes:

> Am I missing something really obvious here?
>
> kore:~/Repos/git (master)$ git ls-files | wc -l
>     2009

You asked it to show the cached paths (default). Your project currently tracks 2009 paths in the index.

> kore:~/Repos/git (master)$ git ls-files -x \* | wc -l
>     2009

You told that '*' is the exclude pattern for carrying out some operation, but you didn't tell what operation you want. You are shown the cached paths (default).

> kore:~/Repos/git (master)$ git ls-files -i -x \* | wc -l
>     2009

You told that '*' is the exclude pattern, you want only paths that match the exclude pattern, and chose to show files in the index (which again is the default) by not saying -o.

I've never found -i useful myself (actually I don't find many options the command has very useful anymore), but the above is how I read the ls-files manual page.