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

Problems with GIT under Windows - "not uptodate"

From
Ddavid.hagood@gmail.com <david.hagood@gmail.com>
Date
Sep 1, 2009, 15:46 UTC
Message-ID
<a21e6af7ee05f56fd8c02d0955af1c72.squirrel@localhost>

I am having a problem trying to support my poor, deluded cow-orkers who use Windows and need to use GIT.

The scenario goes something like this:

They have a local repo, they have changes on their branch, they are staging a commit to the master branch on their local.

They do a "git merge" and the merge has conflicts. They need to undo the merge, so they do a "git reset --hard".

>From that point onward, if they try to access the origin repository (e.g.
"git pull") they get the error message
Error: Entry "Some file name" not uptodate: cannot merge.

We've tried "git reset --hard; git pull ." We've tried "git reset --hard; git checkout -f master". Neither seems to fix this.

We Linux users don't see this.

I conjecture it is something to do with DOS's CR/LF line endings (the files in question are a type of XML file which ALWAYS have CR/LF endings, even under Linux) - perhaps *something* in the GIT processing chain is trying to do a CR/LF -> LF conversion, and screwing things up.

Does anybody have any suggestions on what I am doing wrong (Please, not "you are using Windows")?

Next: Eric Raible
Message 1 of 7 in “Problems with GIT under Windows - "not uptodate"”
  1. david.hagood@gmail.comSep 1, 2009
  2. Eric RaibleSep 1, 2009
  3. Johannes SchindelinSep 1, 2009
  4. Eric RaibleSep 1, 2009
  5. Johannes SchindelinSep 1, 2009
  6. skillzero@gmail.comSep 1, 2009
  7. david.hagood@gmail.comSep 1, 2009

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.