From: Daniel Blendea <bdaniel7@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Michael J Gruber <git@drmicha.warpmail.net>, git@vger.kernel.org
Subject: Re: git pull (Your local changes to ... would be overwritten by merge)
Date: Thu, 17 Jun 2010 14:18:21 +0300 [thread overview]
Message-ID: <AANLkTinWS0zWhh0d-yrb7eWMEeQenoAF8tA6-l9BRP_q@mail.gmail.com> (raw)
In-Reply-To: <vpq4oh1zzfs.fsf@bauges.imag.fr>
Windows 7, did not change anything related to crlf.
I solved the problem with
git fetch --all
git reset --hard origin/master
---
Daniel
On Thu, Jun 17, 2010 at 14:11, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
> Michael J Gruber <git@drmicha.warpmail.net> writes:
>
>> Daniel Blendea venit, vidit, dixit 17.06.2010 11:35:
>>> 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.
>
> Which OS? Do you have any crlf conversion enabled? Any filter set in
> .gitattributes?
>
>> Most likely the remote side did a non-forward push and brought you in
>> that situation.
>
> A non-fast forward push would force a non-fast forward pull,
> possibly/probably with conflicts, but wouldn't trigger this message,
> which is generated before the merge is actually started.
>
> --
> Matthieu Moy
> http://www-verimag.imag.fr/~moy/
>
next prev parent reply other threads:[~2010-06-17 11:18 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
2010-06-17 10:42 ` Michael J Gruber
2010-06-17 11:11 ` Matthieu Moy
2010-06-17 11:18 ` Daniel Blendea [this message]
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=AANLkTinWS0zWhh0d-yrb7eWMEeQenoAF8tA6-l9BRP_q@mail.gmail.com \
--to=bdaniel7@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@drmicha.warpmail.net \
--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).