All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Buchacher <drizzd@aon.at>
To: Michael Johnson <redbeard@mdjohnson.us>
Cc: Miklos Vajna <vmiklos@frugalware.org>, git@vger.kernel.org
Subject: Re: Segfault on merge with 1.6.2.1
Date: Wed, 1 Apr 2009 20:06:27 +0200	[thread overview]
Message-ID: <20090401180627.GA14716@localhost> (raw)
In-Reply-To: <op.urnad7jbso3nzr@sulidor.mdjohnson.us>

On Tue, Mar 31, 2009 at 02:14:21AM -0500, Michael Johnson wrote:
> It would appear that the patch has already been applied to 1.6.2.1.

I don't think it has. But judging from the stack trace this bug is unrelated
to the patch anyways.

If nobody else is dealing with this I'd like to have a look at it. Could you
please send me a copy of the repo.

Thanks,
Clemens

  parent reply	other threads:[~2009-04-01 18:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-28 16:19 Segfault on merge with 1.6.2.1 Michael Johnson
2009-03-29 12:17 ` Miklos Vajna
2009-03-30  2:39   ` Michael Johnson
2009-03-30  7:48     ` Johannes Schindelin
2009-03-30 11:03     ` Miklos Vajna
2009-03-31  7:14       ` Michael Johnson
2009-04-01  5:43         ` Michael Johnson
2009-04-01  9:50           ` Miklos Vajna
2009-04-01 18:06         ` Clemens Buchacher [this message]
2009-04-02  0:33           ` Michael Johnson
2009-04-05  0:46           ` Clemens Buchacher
2009-04-05  0:46             ` [PATCH 1/3] add tests for merging with submodules Clemens Buchacher
2009-04-05  0:46               ` [PATCH 2/3] update cache for conflicting submodule entries Clemens Buchacher
2009-04-05  0:47                 ` [PATCH 3/3] simplify output of conflicting merge Clemens Buchacher
2009-04-05  9:47                   ` Junio C Hamano
2009-04-05 11:50             ` Segfault on merge with 1.6.2.1 Johannes Schindelin
2009-04-06  2:29             ` Michael Johnson
2009-04-06  6:41               ` Clemens Buchacher

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=20090401180627.GA14716@localhost \
    --to=drizzd@aon.at \
    --cc=git@vger.kernel.org \
    --cc=redbeard@mdjohnson.us \
    --cc=vmiklos@frugalware.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.