From: Sebastian Schuberth <sschuberth@gmail.com>
To: git@vger.kernel.org
Subject: Re: Git doesn't detect change, if file modification time is restored to original one
Date: Thu, 23 Jul 2015 09:58:13 +0200 [thread overview]
Message-ID: <55B09E95.4000700@gmail.com> (raw)
In-Reply-To: <CABEDGg8zixeab-CsviAU-fNE1Jmi0ZWbN6=e6Q+-XK3eFv6djA@mail.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
next prev parent reply other threads:[~2015-07-23 7:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 7:29 Git doesn't detect change, if file modification time is restored to original one Konrád Lőrinczi
2015-07-23 7:58 ` Sebastian Schuberth [this message]
2015-07-23 9:14 ` Konrád Lőrinczi
2015-07-23 14:53 ` Konstantin Khomoutov
2015-07-23 15:16 ` Karsten Blees
2015-07-23 17:32 ` Junio C Hamano
2015-07-23 14:17 ` Johannes Schindelin
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=55B09E95.4000700@gmail.com \
--to=sschuberth@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).