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

Git detects changes after new branch created and switched even though files have not been changed

From
JBJared Brank <jared.brank@skaletech.com>
Date
Aug 6, 2014, 15:04 UTC
Message-ID
<a2546f9109674431820b7a98f9570433@BL2PR05MB180.namprd05.prod.outlook.com>
Running on Windows with latest version of Git. 1.9.4. Also had this trouble with 1.8.2 but upgraded hoping it would fix the problem.

When I do a reset on several files, it says they were successfully reverted they still show up as modified when I do a git status. In this case it's just a newline character at the end of the file. I also tried a reset -- hard and they files still show up! What the heck! Help please. In trying to reproduce this, I re-cloned the git repo from the server, which was in the exact clean state before I started last time. No files have been modified after cloning, all are identical. Then, I created a new branch (totally new, not tracking a remote branch). Viola - I now have these files show up in my git status as modified. Please note that these are files that have been tracked for several previous commits. Just to clarify - the only command I ran to make this happen is: git checkout -b newbranch

And GitGui shows the files as identical even when compare whitespace is turned on.
Next: Jakub Narębski
Message 1 of 2 in “Git detects changes after new branch created and switched even though files have not been changed”
  1. Jared BrankAug 6, 2014
  2. Jakub NarębskiAug 6, 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.