From: Konstantin Khomoutov <kostix+git@007spb.ru>
Date: Thu, 23 Jul 2015 14:53:42 GMT
Subject: Re: Git doesn't detect change, if file modification time is restored to original one
Message-ID: <20150723175342.77f635820fb9f1b69a73d39a@domain007.com>
In-Reply-To: <CABEDGg_R49K61wiV9SsTnLS9SztHDjEQhOHjwzYn2JJwrrb-KA@mail.gmail.com>

On Thu, 23 Jul 2015 11:14:11 +0200
Konrád Lőrinczi <klorinczi@gmail.com> wrote:

[...]
> I accept these solutions as workarounds, but the real solution would
> be: Dev suggestions:
> 1) Add a --force-reread option to git status, so user can force
> reread tree. git status --force-reread
> 
> 2) Add status.force-reread (true or false) option to .git/config so
> user can set this variable permanently for a repo.
> status.force-reread = false (should be default)
> 
> Could be possible to implement 1) and 2) features to next git release?

Could you explain what's your real use case with preserving mtimes
while changing the files?  I mean, implementing "mtime-stability"
in your tools appears to be a good excersize in programming but what
real-world problem does it solve?

I'm asking because if you are not going to implement the changes to
Git you suggested yourself, then someone else should be *convinced* to
do so.  So far, your trouble appears to be too artifical to bother.