From: Christoph Haas <haas@debian.org>
To: git@vger.kernel.org
Subject: Strange merge failure (would be overwritten by merge / cannot merge)
Date: Fri, 04 Sep 2009 22:28:36 +0200 [thread overview]
Message-ID: <4AA17874.7090905@debian.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear list,
I'm struggling with a pretty simple Git repository where I maintain one
of my Debian packages. It has two branches:
- upstream (contains the unaltered original software unpacked from
a .tar.gz)
- master (derived from upstream plus Debian specific changes)
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.
So it looks like the 'cream-abbr-eng.vim' file has been altered. And it
contains some non-ASCII characters (it's a VIM script file) so perhaps
automatic merging fails. But can't I just tell Git to screw my file in
the 'master' branch and just overwrite my file? No merge strategy helped
me accomplish that.
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
Help welcome. I'm no Git guru and totally at a loss here. As a last
resort I would start from scratch losing all of my Git history.
Kindly
Christoph
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkqheHQACgkQCV53xXnMZYZSaQCdF4JovwKUx1FIOq82+joGUIlq
a7UAoIoC2mm2L6Pv7MvZGzOIRNgktb2B
=pklM
-----END PGP SIGNATURE-----
next reply other threads:[~2009-09-04 20:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 20:28 Christoph Haas [this message]
2009-09-04 23:45 ` Strange merge failure (would be overwritten by merge / cannot merge) David Aguilar
2009-09-05 13:07 ` Christoph Haas
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=4AA17874.7090905@debian.org \
--to=haas@debian.org \
--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).