Dear diary, on Tue, Jul 12, 2005 at 07:52:18AM CEST, I got a letter
where Marc Singer [EMAIL PROTECTED] told me that...
# 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
Marc Singer [EMAIL PROTECTED] 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
On Tue, Jul 12, 2005 at 01:14:24AM -0700, Junio C Hamano wrote:
Marc Singer [EMAIL PROTECTED] 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,
Matthias Urlichs smurf at smurf.noris.de writes:
Hi, Marc Singer wrote:
# git-update-cache `git-diff-cache | cut -f2`
g-d-c should have an option to print file names only. All that cutting
and argument-backtick-ing gets pretty nasty when there are a lot of files,
or if they contain
4 matches
Mail list logo
