From: Karl Chen <quarl@cs.berkeley.edu>
To: Git mailing list <git@vger.kernel.org>
Subject: git-update-index --refresh man page
Date: Tue, 02 Sep 2008 10:54:51 -0700 [thread overview]
Message-ID: <quack.20080902T1054.lthwshul9g4@roar.cs.berkeley.edu> (raw)
I suggest expanding/clarifying the documentation for
git-update-index --refresh. For example:
"If a file's mtime has changed, but its contents have not,
then update-index --refresh will update the index to reflect
the new mtimes."
reply other threads:[~2008-09-02 17:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=quack.20080902T1054.lthwshul9g4@roar.cs.berkeley.edu \
--to=quarl@cs.berkeley.edu \
--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).