From: Dragos Foianu <dragos.foianu@gmail.com>
To: git@vger.kernel.org
Subject: Re: [BUG] Segfault on git describe
Date: Sat, 22 Mar 2014 10:18:44 +0000 (UTC) [thread overview]
Message-ID: <loom.20140322T111539-312@post.gmane.org> (raw)
In-Reply-To: 20140320233307.GB7774@sigill.intra.peff.net
Jeff King <peff <at> peff.net> writes:
>
> So I think we'd be happy to see it converted to an iterative process
> (probably with a stack on the heap). In addition to name-rev, I believe
> that "tag --contains" will recurse down the longest history path, too (I
> think there may have been experimental patches for the latter, but you'd
> have to search the list archive).
>
> -Peff
>
Alright. I'll look into it and hopefully have a patch by the end of the weekend.
-Dragos
prev parent reply other threads:[~2014-03-22 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 10:48 [BUG] Segfault on git describe Sylvestre Ledru
2014-03-19 12:03 ` Sylvestre Ledru
2014-03-19 22:34 ` Dragos Foianu
2014-03-20 23:33 ` Jeff King
2014-03-22 10:18 ` Dragos Foianu [this message]
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=loom.20140322T111539-312@post.gmane.org \
--to=dragos.foianu@gmail.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 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).