From: "Carlos Martín Nieto" <cmn@dwim.me>
To: Andy Lowry <andy.work@nglowry.com>
Cc: git@vger.kernel.org
Subject: Re: BUG in git diff-index
Date: Thu, 31 Mar 2016 15:57:47 +0200 [thread overview]
Message-ID: <1459432667.2124.2.camel@dwim.me> (raw)
In-Reply-To: <loom.20160331T143733-916@post.gmane.org>
On Thu, 2016-03-31 at 12:39 +0000, Andy Lowry wrote:
> Following transcript illustrates what I believe to be a bug in git
> diff-
> index. The session used a git built from latest source, located in
> /tmp/git/git.
>
> 1. New repo, create empty file A, commit changes.
> 2. touch A
> 3. git diff-index reports A has changed, and reports bogus
> destination
> SHA
> 4. This is stable behavior until next step
This is expected and matches the documentation. See the bit starting
with
OPERATING MODES
You can choose whether you want to trust the index file entirely (using the --cached flag) or ask the diff
logic to show any files that don’t match the stat state as being "tentatively changed". Both of these
operations are very useful indeed.
The next two sections describe what you are seeing. The default is non-
cached mode which also shows files which don't match the stat data in
the index (which you've changed by touching the file).
Cheers,
cmn
next prev parent reply other threads:[~2016-03-31 13:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 12:39 BUG in git diff-index Andy Lowry
2016-03-31 13:57 ` Carlos Martín Nieto [this message]
2016-03-31 14:05 ` Jeff King
2016-03-31 14:12 ` Andy Lowry
2016-03-31 14:27 ` Jeff King
2016-03-31 19:30 ` Andy Lowry
2016-03-31 20:39 ` Junio C Hamano
2017-09-26 19:46 ` Marc Herbert
2017-09-26 20:11 ` Eric Wong
2017-09-26 23:27 ` Google indexing https://public-inbox.org/git (was: BUG in git diff-index) Marc Herbert
2017-09-27 21:06 ` Wrong -dirty suffix set by setlocalversion " Marc Herbert
2018-05-24 23:03 ` Mike Mason
2018-05-25 3:50 ` Marc Herbert
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=1459432667.2124.2.camel@dwim.me \
--to=cmn@dwim.me \
--cc=andy.work@nglowry.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.
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).