Re: Why is there no git-update-cache --modified (aka I give up)

From: Marc Singer <elf@buici.com>
Date: Jul 12, 2005, 15:53 UTC
Message-ID: <20050712155316.GA5841@buici.com>
In-Reply-To: <7v7jfwbfvj.fsf@assigned-by-dhcp.cox.net>

On Tue, Jul 12, 2005 at 01:14:24AM -0700, Junio C Hamano wrote:

Show 11 quoted lines

> Marc Singer <elf@buici.com> writes:
> 
> >   # git-diff-cache HEAD
> >
> > is really nice.  But, do I really have to invoke git-update-cache with
> > every modified file?  I could write a script to cul the filenames from
> > git-diff-cache, but I'm having a hard time believing that that is how
> > others are preparing their commits.
> 
> Me too.  By the way, I think you mean diff-files not
> diff-cache.

No, I mean git-diff-cache.  I find that this works pretty well, though.

  # git-update-cache `git-diff-cache | cut -f2`

It looks like the same thing works for git-diff-files.

  # git-update-cache `git-diff-files | cut -f2`

This seems to agree with the way you handle things.

Similarly, there is the need to determine which files are new to the tree. This isn't much of a burden when creating files in the tree, but can be bothersome when using patch since git-apply is conservative about fuzz.