From: Christoph Haas <email@christoph-haas.de>
To: git@vger.kernel.org
Subject: Re: Strange merge failure (would be overwritten by merge / cannot merge)
Date: Sat, 05 Sep 2009 15:07:32 +0200 [thread overview]
Message-ID: <h7tnqm$hv6$1@ger.gmane.org> (raw)
In-Reply-To: <20090904234552.GA43797@gmail.com>
David Aguilar schrieb:
> On Fri, Sep 04, 2009 at 10:28:36PM +0200, Christoph Haas wrote:
>> Now I imported a new upstream version into the upstream branch. And then
>> tried to merge the 'upstream' branch into the 'master' branch to work on
>> it. And suddenly I get this error:
>>
>> error: Entry 'cream-abbr-eng.vim' would be overwritten by merge.
>> Cannot merge.
>>
>> To reproduce my problem:
>>
>> $> git clone git://git.workaround.org/cream
>> $> cd cream
>> $> git merge origin/upstream
>> error: Entry 'cream-abbr-eng.vim' would be overwritten by merge.
>> Cannot merge.
>> fatal: merging of trees 70008c82f82a7985531aa2d039c03fdf944ea267 and
>> 78d3a35e300434d6369424dd873bb587beacfaa4 failed
>
> Very odd indeed!
>
> $ git version
> git version 1.6.4.2.264.g79b4f
>
> I was able to workaround it:
>
> $ rm *
> $ git add -u
> $ git merge origin/upstream
Thank you. I had to "rm -r addons", too, but the general hint helped me
a lot.
> I've never run into this before.
> I think it has to do with all the renamed files.
> It looks like you're running into ain unfortunate edge case.
Actually I'm not aware of any renames. But I don't claim that I always
know what I'm doing. :)
> Does anyone else on the list have any insights?
I'd be curious, too.
Kindly
Christoph
next prev parent reply other threads:[~2009-09-05 13:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 20:28 Strange merge failure (would be overwritten by merge / cannot merge) Christoph Haas
2009-09-04 23:45 ` David Aguilar
2009-09-05 13:07 ` Christoph Haas [this message]
2009-09-05 17:46 ` Junio C Hamano
2009-09-06 0:33 ` Junio C Hamano
2009-09-06 8:21 ` Junio C Hamano
2009-09-06 18:18 ` Linus Torvalds
2009-09-06 19:39 ` Junio C Hamano
2009-09-06 19:54 ` Linus Torvalds
2009-09-06 20:36 ` Junio C Hamano
2009-09-06 20:42 ` Linus Torvalds
2009-09-06 20:58 ` Linus Torvalds
2009-09-06 21:17 ` Junio C Hamano
2009-09-06 21:37 ` Linus Torvalds
2009-09-06 22:49 ` Linus Torvalds
2009-09-06 21:11 ` Junio C Hamano
2009-09-05 6:40 ` unpack-trees traversing with index quite broken Junio C Hamano
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='h7tnqm$hv6$1@ger.gmane.org' \
--to=email@christoph-haas.de \
--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).