From: Jon Loeliger <jdl@freescale.com>
To: git@vger.kernel.org
Subject: Re: [BUG] ProgramError: merge ... .merge_file_4CPoEQ: No such file
Date: Tue, 06 Dec 2005 10:47:50 -0600 [thread overview]
Message-ID: <E1Ejfyo-0003ae-2K@jdl.com> (raw)
In-Reply-To: 20051206163314.GA6112@c165.ib.student.liu.se
> It seems that changes has been committed to
> Documentation/git-read-tree.txt in both the jdl branch and in
> origin.
Yes.
> This shouldn't cause any problems but git-merge-recursive
> (which currently is the default merge strategy) uses merge(1) to do
> the file-level merging and it seems like merge(1) can't be found on
> your system.
>
> Do you have merge(1) installed? More appropriately, is merge in your
> path? If it isn't installed it can usually be found in the rcs package
> in your distribution.
Oh wow. Exactly correct.
Here's Jon building up the new Ubuntu box, and thinking, "I'll
be using git, so I don't need to install RCS or CVS anymore." :-)
After installing RCS, here's what we get:
jdl@ubuntu:/usr/src/git-core$ git reset --hard jdl
jdl@ubuntu:/usr/src/git-core$ git pull . origin
Trying really trivial in-index merge...
fatal: Merge requires file-level merging
Nope.
Merging HEAD with be61db922a230ae2638c27c071ee4b8c98f01f72
Merging:
4baf91676c2462796137e93917c75f2e14ebb877 Added documentation for few missing options.
be61db922a230ae2638c27c071ee4b8c98f01f72 git-merge-one-file: resurrect leading path creation.
found 1 common ancestor(s):
23c99d84601316c1e51ebc1f0b9bec5cddd011fb git-mv to work with Perl 5.6
Auto-merging Documentation/git-read-tree.txt
CONFLICT (content): Merge conflict in Documentation/git-read-tree.txt
Automatic merge failed/prevented; fix up by hand
Thanks!
jdl
next reply other threads:[~2005-12-06 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 16:47 Jon Loeliger [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-06 14:03 [BUG] ProgramError: merge ... .merge_file_4CPoEQ: No such file Jon Loeliger
2005-12-06 16:33 ` Fredrik Kuivinen
2005-12-06 16:51 ` 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=E1Ejfyo-0003ae-2K@jdl.com \
--to=jdl@freescale.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.