Based on [1] I found some solutions which makes the changed files appear again as changed: a) touch -m --date=01/01/1980 .git/index So it is a touch, but only a single one, instead of touching all the files in the work dir.
b) git read-tree HEAD Also working well. 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? Thanks, Konrad Lorinczi [1] https://github.com/msysgit/git/issues/312 2015-07-23 9:58 GMT+02:00 Sebastian Schuberth <sschube...@gmail.com>: > On 7/23/2015 9:29, Konrád Lőrinczi wrote: > >> Interesting, that git status doesn't show replaced changes, if the >> mtime is same as original. > > See the somewhat related FAQ entry at [1] and also the lengthy discussion at > [2] about a similar issue. That said, deleting the .git/index file should > make these files appear as modified. > > [1] > https://git.wiki.kernel.org/index.php/Git_FAQ#Why_isn.27t_Git_preserving_modification_time_on_files.3F > [2] https://github.com/msysgit/git/issues/312 > > Regards, > Sebastian > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
