git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Singer <elf@buici.com>
To: git@vger.kernel.org
Subject: Why is there no git-update-cache --modified (aka I give up)
Date: Mon, 11 Jul 2005 22:52:18 -0700	[thread overview]
Message-ID: <20050712055218.GA18192@buici.com> (raw)

  # 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.

             reply	other threads:[~2005-07-12  5:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12  5:52 Marc Singer [this message]
2005-07-12  7:26 ` Why is there no git-update-cache --modified (aka I give up) Petr Baudis
2005-07-12  8:14 ` Junio C Hamano
2005-07-12 15:53   ` Marc Singer
2005-07-12 16:16     ` Matthias Urlichs
2005-07-12 20:51       ` Junio C Hamano
2005-07-13 19:45         ` [PATCH] diff-stages: support "-u" as a synonym for "-p" Junio C Hamano
2005-07-13 19:45         ` [PATCH] git-diff-*: --name-only and --name-only-z Junio C Hamano
2005-07-13 19:52         ` [PATCH] Clean up diff option descriptions Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050712055218.GA18192@buici.com \
    --to=elf@buici.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).