git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Blendea <bdaniel7@gmail.com>
To: "Santi Béjar" <santi@agolina.net>
Cc: git@vger.kernel.org
Subject: Re: git pull (Your local changes to ... would be overwritten by  merge)
Date: Thu, 17 Jun 2010 13:20:31 +0300	[thread overview]
Message-ID: <AANLkTinQkCH5OhnoerCJs2x_2uChwaqVPApeezwcYy1o@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimakxkEzFHSwezpXelLV171zGFEQULNEVpJlrah@mail.gmail.com>

I have no idea, I know git just barely to be able to update my copy
once in a while, then build it to get the binaries.
I didn't modified anything and the build script builds the binaries in
a different location.

The file which threw the first error was already in my copy and it was
modified in the remote branch.
---
Daniel



On Thu, Jun 17, 2010 at 12:46, Santi Béjar <santi@agolina.net> wrote:
> On Thu, Jun 17, 2010 at 11:35 AM, Daniel Blendea <bdaniel7@gmail.com> wrote:
>> 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
>

  reply	other threads:[~2010-06-17 10:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTinokUxiDdetcrsrlSExQ7hmhLS5szbTt9KzGKr_@mail.gmail.com>
2010-06-17  9:35 ` git pull (Your local changes to ... would be overwritten by merge) Daniel Blendea
2010-06-17  9:46   ` Santi Béjar
2010-06-17 10:20     ` Daniel Blendea [this message]
2010-06-17 10:42   ` Michael J Gruber
2010-06-17 11:11     ` Matthieu Moy
2010-06-17 11:18       ` Daniel Blendea
2010-06-17 11:58         ` Michael J Gruber
2010-06-17 15:21           ` Matthieu Moy
2010-06-18  7:44             ` Eyvind Bernhardsen

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=AANLkTinQkCH5OhnoerCJs2x_2uChwaqVPApeezwcYy1o@mail.gmail.com \
    --to=bdaniel7@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=santi@agolina.net \
    /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).