public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Thomas Rast <trast@inf•ethz.ch>
To: Yann Hodique <yann.hodique@gmail•com>
Cc: <git@vger•kernel.org>
Subject: Re: consistency problem on ZFS
Date: Sun, 28 Apr 2013 21:33:21 +0200	[thread overview]
Message-ID: <87k3nme9ha.fsf@hexa.v.cablecom.net> (raw)
In-Reply-To: <m2bo8yxyg2.fsf@jarvis.hodique.info> (Yann Hodique's message of "Sun, 28 Apr 2013 20:11:25 +0100")

Yann Hodique <yann.hodique@gmail•com> writes:

> I have a weird problem that seems to manifest itself only on ZFS
> (actually the Zevo distribution, on OSX). With git 1.8.2.1 by the way.
> I just switched to ZFS, so I can't blame that particular version of git.
>
> "Sometimes" (I'd say something like 10-15% of the time, fairly
> reproducible anyway), "git diff-files" will see changes that don't exist
> for some time, then will catch up with the actual state of the file:
>
> $ git checkout next; git diff-files; git checkout next; git diff-files
> Already on 'next'
> :100644 100644 bd774cccaa14e061c3c26996567ee28f4f77ec80 0000000000000000000000000000000000000000 M	magit.el
> Already on 'next'
> $

git-diff-files doesn't refresh the index.  Why are you using it?  It's
the plumbing version of 'git diff' (without args), which does the same
but *does* refresh the index.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2013-04-28 19:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-28 19:11 consistency problem on ZFS Yann Hodique
2013-04-28 19:33 ` Thomas Rast [this message]
2013-04-28 19:44   ` Yann Hodique
2013-04-28 20:12 ` John Szakmeister
2013-04-28 20:21   ` Yann Hodique
2013-04-28 21:33 ` Junio C Hamano
2013-04-29 17:55   ` Yann Hodique
2013-04-29 18:01     ` Junio C Hamano
2013-04-29 18:16       ` Yann Hodique

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=87k3nme9ha.fsf@hexa.v.cablecom.net \
    --to=trast@inf$(echo .)ethz.ch \
    --cc=git@vger$(echo .)kernel.org \
    --cc=yann.hodique@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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