From: Jay Soffian <jaysoffian@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Elijah Newren <newren@gmail.com>, git@vger.kernel.org
Subject: Re: [BUG] merge-recursive triggered "BUG"
Date: Thu, 19 May 2011 21:17:34 -0400 [thread overview]
Message-ID: <BANLkTinG329ZBdf0TgnwA1m8Uo+6OZv-ow@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimNnRrJ_2UJUSWWd1QS=e0YH2p=_Q@mail.gmail.com>
On Thu, May 19, 2011 at 9:14 PM, Jay Soffian <jaysoffian@gmail.com> wrote:
> I just ran into this. It's not in a repo I can share however. But, why
> did b2c8c0a make it into master with this known issue?
Sorry, let me clarify. I got the:
error: addinfo_cache failed for path '...'
line, but not the BUG. I can try to bisect git if this is a different issue.
j.
next prev parent reply other threads:[~2011-05-20 1:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 0:39 [BUG] merge-recursive triggered "BUG" Junio C Hamano
2011-03-17 21:45 ` Junio C Hamano
2011-03-18 6:07 ` [PATCH] merge-recursive: tweak magic band-aid Junio C Hamano
2011-03-21 18:24 ` Elijah Newren
2011-05-20 1:14 ` [BUG] merge-recursive triggered "BUG" Jay Soffian
2011-05-20 1:17 ` Jay Soffian [this message]
2011-05-20 3:21 ` Junio C Hamano
2011-05-20 12:29 ` Jay Soffian
2011-05-20 13:00 ` Jay Soffian
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=BANLkTinG329ZBdf0TgnwA1m8Uo+6OZv-ow@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
/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).