[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <d9b4725b-3204-03af-1bc2-6469bb815c63@intel.com>
Date: Tue, 26 Sep 2017 12:46:13 -0700
From: Marc Herbert <Marc.Herbert@...el.com>
To: Junio C Hamano <gitster@...ox.com>,
Andy Lowry <andy.work@...owry.com>
Cc: Jeff King <peff@...f.net>, git <git@...r.kernel.org>,
Christian Kujau <lists@...dbynature.de>, josh@...htriplett.org,
michael.w.mason@...el.com, linux-kernel@...r.kernel.org
Subject: Re: BUG in git diff-index
On 31/03/16 13:39, Junio C Hamano wrote:
> Andy Lowry <andy.work@...owry.com> writes:
>
>> So I think now that the script should do "update-index --refresh"
>> followed by "diff-index --quiet HEAD". Sound correct?
>
> Yes. That has always been one of the kosher ways for any script to
> make sure that the files in the working tree that are tracked have
> not been modified relative to HEAD (assuming that the index matches
> HEAD).
Too bad kernel/scripts/setlocalversion didn't get the memo:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cdf2bc632ebc9ef51
> scripts/setlocalversion on write-protected source tree (2013)
> I don't see how removing "git update-index" could do any harm.
This causes a spurious "-dirty" suffix when building from a directory copy
(as Mike learned the hard way)
----
PS: I used NNTP and http://dir.gmane.org/gmane.comp.version-control.git
to quickly find this old thread (what could we do without NNTP?). Then
I googled for a web archive of this thread and Google could only find
this one: http://git.661346.n2.nabble.com/BUG-in-git-diff-index-tt7652105.html#none
Is there a robots.txt to block indexing on
https://public-inbox.org/git/1459432667.2124.2.camel@dwim.me ?
Powered by blists - more mailing lists