Re: git-diff new files (without using index)

From: Shawn O. Pearce <spearce@spearce.org>
Date: Aug 5, 2007, 04:08 UTC
Message-ID: <20070805040841.GG9527@spearce.org>
In-Reply-To: <87r6miljfr.fsf@catnip.gol.com>

Miles Bader <miles@gnu.org> wrote:

> Thanks for the tip (I guess I can roll my own "git-diff-uncached"
> script)!

Indeed, Git is quite scriptable.  ;-)

Show 5 quoted lines

> The above sort of quirkiness does seem kind of a wart though; in my
> (admittedly limited, using git) experience this sort of thing really
> reduces the utility of the index, and I often end up feeling like it's
> just getting in the way as a result.  Does adding something like a
> "git-diff -N" option seem a _bad_ idea?

I'm not interested in such an option. Typically if I want a diff on a new untracked file I actually want that file in my next commit anyway. So I'm usually staging it into the index along with everything else that I have modified. In which case this quirkiness isn't really a quirk at all. Its just not an issue to me.

If you want to try adding it, go right ahead. The source for git is stored in git and available from many places. :-)

-- 
Shawn.