git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: david.hagood@gmail.com
To: git@vger.kernel.org
Subject: Problems with GIT under Windows - "not uptodate"
Date: Tue, 1 Sep 2009 10:46:39 -0500 (CDT)	[thread overview]
Message-ID: <a21e6af7ee05f56fd8c02d0955af1c72.squirrel@localhost> (raw)

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")?

             reply	other threads:[~2009-09-01 15:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-01 15:46 david.hagood [this message]
2009-09-01 16:52 ` Problems with GIT under Windows - "not uptodate" Eric Raible
2009-09-01 22:56   ` Johannes Schindelin
2009-09-01 23:16     ` Eric Raible
2009-09-01 23:19       ` Johannes Schindelin
2009-09-01 18:19 ` skillzero
2009-09-01 18:25   ` david.hagood

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=a21e6af7ee05f56fd8c02d0955af1c72.squirrel@localhost \
    --to=david.hagood@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).