From: Junio C Hamano <gitster@pobox•com>
To: Michael Haggerty <mhagger@alum•mit.edu>
Cc: Petr Stodulka <pstodulk@redhat•com>, git@vger•kernel.org
Subject: Re: [BUG] [PATCH] infinite loop due to broken symlink
Date: Wed, 25 Mar 2015 16:21:58 -0700 [thread overview]
Message-ID: <xmqq1tkc1x49.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <55133C63.2010805@alum.mit.edu> (Michael Haggerty's message of "Wed, 25 Mar 2015 23:53:23 +0100")
Michael Haggerty <mhagger@alum•mit.edu> writes:
> Thanks for the bug report. I can confirm the problem. In fact, I noticed
> the same problem when I was working on a refactoring in the area, but I
> still haven't submitted those patches.
Thanks. It is nice to know that the refs.c API refactoring is still
being worked on.
next prev parent reply other threads:[~2015-03-25 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 16:04 [BUG] [PATCH] infinite loop due to broken symlink Petr Stodulka
2015-03-25 22:53 ` Michael Haggerty
2015-03-25 23:21 ` Junio C Hamano [this message]
2015-03-26 9:32 ` Petr Stodulka
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=xmqq1tkc1x49.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=mhagger@alum$(echo .)mit.edu \
--cc=pstodulk@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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