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

Re: git pull (Your local changes to ... would be overwritten by merge)

From
SBSanti Béjar <santi@agolina.net>
Date
Jun 17, 2010, 09:46 UTC
Message-ID
<AANLkTimakxkEzFHSwezpXelLV171zGFEQULNEVpJlrah@mail.gmail.com>
In-Reply-To
<AANLkTimeIWseETfYiMajIqesjJ_p55pRislnQQIaCrbG@mail.gmail.com>
On Thu, Jun 17, 2010 at 11:35 AM, Daniel Blendea <bdaniel7@gmail.com> wrote:
Show 9 quoted lines
> Hello,
>
> A while ago I have cloned on my computer a git repo.
> Since then, the developers have modified several files in the repo.
> Now I want to update my copy with the latest changes.
>
> I do 'git pull' but I get 'Your local changes to .... would be
> overwritten by merge.  Aborting.'
> I didn't modified any local file. I tried using 'git stash save' but no luck.
Are they known to git? What is their status (git status)?

If they are not known to git, it seams that there are *new* files both in the remote branch and the working copy (new files in the working copy are not saved with 'git stash save').

I would rename/mv the conflicting new files in the working copy, perform the pull and maybe compare the new files from the branch with the ones from the working copy.

HTH, Santi

Previous: Daniel BlendeaNext: Daniel Blendea
Message 2 of 9 in “git pull (Your local changes to ... would be overwritten by merge)”
  1. Daniel BlendeaJun 17, 2010
  2. Santi BéjarJun 17, 2010
  3. Daniel BlendeaJun 17, 2010
  4. Michael J GruberJun 17, 2010
  5. Matthieu MoyJun 17, 2010
  6. Daniel BlendeaJun 17, 2010
  7. Michael J GruberJun 17, 2010
  8. Matthieu MoyJun 17, 2010
  9. Eyvind BernhardsenJun 18, 2010

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.