On Thu, 23 Jul 2015 11:14:11 +0200 Konrád Lőrinczi <klorinczi@xxxxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html