From: Petr Baudis <pasky@suse.cz>
To: Marc Singer <elf@buici.com>
Cc: git@vger.kernel.org
Subject: Re: Why is there no git-update-cache --modified (aka I give up)
Date: Tue, 12 Jul 2005 09:26:29 +0200 [thread overview]
Message-ID: <20050712072629.GA6363@pasky.ji.cz> (raw)
In-Reply-To: <20050712055218.GA18192@buici.com>
Dear diary, on Tue, Jul 12, 2005 at 07:52:18AM CEST, I got a letter
where Marc Singer <elf@buici.com> 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
> git-diff-cache, but I'm having a hard time believing that that is how
> others are preparing their commits.
It is. :-) It's only that they have cool scripts to do it, e.g.
cg-commit. (You have to enumerate the files explicitly for
git-commit-script as well, IIRC.)
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
<Espy> be careful, some twit might quote you out of context..
next prev parent reply other threads:[~2005-07-12 7:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 5:52 Why is there no git-update-cache --modified (aka I give up) Marc Singer
2005-07-12 7:26 ` Petr Baudis [this message]
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=20050712072629.GA6363@pasky.ji.cz \
--to=pasky@suse.cz \
--cc=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).