From: Junio C Hamano <gitster@pobox.com>
To: Michael Brown <michael.brown@discourse.org>
Cc: git@vger.kernel.org
Subject: Re: "git diff-files" command reports differences that don't exist
Date: Fri, 05 Mar 2021 13:49:30 -0800 [thread overview]
Message-ID: <xmqqa6rh9sph.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <4210f5f1-dd7e-f425-6ab2-e220a33e82bf@discourse.org> (Michael Brown's message of "Fri, 5 Mar 2021 14:28:20 -0500")
Michael Brown <michael.brown@discourse.org> writes:
> What did you do before the bug happened? (Steps to reproduce your issue)
>
> 1. Be in any existing repository in a clean state (I tested with 2 existing
> repositories and 1 completely fresh)
> 1. run `git diff-files`, see no output
> 1. touch an existing file: `touch a`
> 1. run `git diff-files`
This is totally expected behaviour. In general when you are working
with plumbing commands like diff-files and diff-index, you are
expected to do "update-index --refresh" upfront.
A plumbing command "git diff" has an equivalent of "update-index
--refresh" built into it, but the plumbing commands are designed
to be used in scripts, and in order to allow scripting programmers
to avoid making unnecessary "update-index --refresh", e.g.
git update-index --refresh
git diff-files | use diff-files output
git diff-index | use diff-index output
they leave it the responsibility of the calling script (or the end
user who directly use them from the command line) to refresh the
cached stat information as necessary.
next prev parent reply other threads:[~2021-03-05 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 19:28 "git diff-files" command reports differences that don't exist Michael Brown
2021-03-05 21:49 ` Junio C Hamano [this message]
2021-03-05 22:18 ` Eric Sunshine
2021-03-05 22:28 ` Junio C Hamano
2021-03-05 22:20 ` Michael Brown
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqa6rh9sph.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=michael.brown@discourse.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).