From: Brian Moran <bmoran@onehub.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Bus Error- git merge
Date: Fri, 30 Jan 2009 16:05:52 -0800 [thread overview]
Message-ID: <C5A8D5E0.E29D%bmoran@onehub.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0901301950100.3586@pacific.mpi-cbg.de>
With subsequent changes to the merged-to repository, the bug does not
manifest. I will attempt to reproduce when we encounter it next.
On 1/30/09 10:57 AM, "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
wrote:
> Hi,
>
> On Fri, 30 Jan 2009, Brian Moran wrote:
>
>> I am getting a bus error on a git merge, including the more recent versions.
>> Following the instructions from a bug August, I got the latest sources,
>> compiled them up, and executed the merge in the debugger to repro. Here¹s
>> what I found:
>
> Is it possible that your branch has submodules?
>
next prev parent reply other threads:[~2009-01-31 0:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 18:15 Bus Error- git merge Brian Moran
2009-01-30 18:57 ` Johannes Schindelin
2009-01-31 0:05 ` Brian Moran [this message]
2009-02-01 22:48 ` Johannes Schindelin
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=C5A8D5E0.E29D%bmoran@onehub.com \
--to=bmoran@onehub.com \
--cc=Johannes.Schindelin@gmx.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).