From: Jonathan Nieder <jrnieder@gmail.com>
To: yun sheng <uewing@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Found a "bug" in git 1.9.0 but can't reproduce it without copyrighted source code.
Date: Thu, 27 Mar 2014 18:40:22 -0700 [thread overview]
Message-ID: <20140328014022.GO15625@google.com> (raw)
In-Reply-To: <CA+fYBFdzC-_B2Qfk8Hg0pLUNy4oayySs+8B3vWq7uuBeAx9eJQ@mail.gmail.com>
Hi,
yun sheng wrote:
> these two files have the same timestamp, the same size, bug slightly
> different contents.
How did they get the same timestamp?
[...]
> Git I'm using is msysgit 1.9.0 on windows 7
Unixy operating systems have other fields like inode number and ctime
that make it possible to notice that a file might have been changed
without actually rereading it. Unfortunately Git for Windows is
limited to what's in the WIN32_FILE_ATTRIBUTE_DATA which means the
size, mtime, and mode are basically all it has to go by.
Do you know of some other Windows API call that could help?
Hope that helps,
Jonathan
next prev parent reply other threads:[~2014-03-28 1:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 0:45 Found a "bug" in git 1.9.0 but can't reproduce it without copyrighted source code yun sheng
2014-03-28 1:04 ` Trần Ngọc Quân
[not found] ` <CA+fYBFdsp4z5T42wEiQ-0X88eK4UhJLx+Ofum_RYEf-g8a3SbA@mail.gmail.com>
2014-03-28 1:40 ` Fwd: " yun sheng
2014-03-28 1:40 ` Jonathan Nieder [this message]
2014-03-28 1:45 ` yun sheng
2014-03-28 1:59 ` Git doesn't notice file has changed (Re: Found a "bug" in git 1.9.0 but can't reproduce it without copyrighted source code.) Jonathan Nieder
2014-03-28 2:06 ` yun sheng
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=20140328014022.GO15625@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=uewing@gmail.com \
/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).