git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Found a "bug" in git 1.9.0 but can't reproduce it without copyrighted source code.

From
yun sheng <uewing@gmail.com>
Date
Mar 28, 2014, 00:45 UTC
Message-ID
<CA+fYBFdzC-_B2Qfk8Hg0pLUNy4oayySs+8B3vWq7uuBeAx9eJQ@mail.gmail.com>
Hi,

I found git sometimes can't detect working trees changes. But I can only reproduce this problem on several specific files, unfortunately these files are copyrighted source files so I can't send them to you. Is there anything I can do to narrow the problem and finally reproduce the bug without these commercial files?

I posted a question on stackoverflow which shows the process.
http://stackoverflow.com/questions/22684163/cant-reproduce-a-bug-in-git-without-a-specific-file
Actually what I'm doing is:

git init " copy the first version of file into the working tree. git add . git commit -m 'init' " copy and replace the file into working tree. git status

and nothing is reported by git.

these two files have the same timestamp, the same size, bug slightly different contents. These files were generated by `git difftool -d` I just manually copied them out from the temp directory just for future review.

Git I'm using is msysgit 1.9.0 on windows 7

Best regards, Sheng Yun

Next: Trần Ngọc Quân
Message 1 of 7 in “Found a "bug" in git 1.9.0 but can't reproduce it without copyrighted source code.”
  1. yun shengMar 28, 2014
  2. Trần Ngọc QuânMar 28, 2014
  3. Jonathan NiederMar 28, 2014
  4. yun shengMar 28, 2014
  5. 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, Mar 28, 2014
  6. yun shengMar 28, 2014
  7. Fwd: Found a "bug" in git 1.9.0 but can't reproduce it without copyrighted source code.yun sheng, Mar 28, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.