From: Derrick Stolee <stolee@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Segfault in master due to 4fbcca4eff
Date: Fri, 21 Sep 2018 10:53:30 -0400 [thread overview]
Message-ID: <5e7e6519-21c1-daff-65a5-7d2ca5e1dbd4@gmail.com> (raw)
In-Reply-To: <87o9cqkj6p.fsf@evledraar.gmail.com>
On 9/21/2018 10:40 AM, Ævar Arnfjörð Bjarmason wrote:
> On Fri, Sep 21 2018, Derrick Stolee wrote:
>
>>
>> This error was reported by Peff [1] and fixed in [2], but as stated
>> [3] I was waiting for more review before sending a v3. I'll send that
>> v3 shortly, responding to the feedback so far.
>>
>> -Stolee
>>
>> [1]
>> https://public-inbox.org/git/0bf9103c-9377-506b-7ad7-e5273d8e94fc@gmail.com/T/#u
>>
>> [2] https://public-inbox.org/git/pull.39.git.gitgitgadget@gmail.com/
>>
>> [3]
>> https://public-inbox.org/git/8d6061de-1654-577c-40c6-211dbd03aa36@gmail.com/
> Thanks and sorry for the duplicate report. I can confirm that applying
> the v2 of that fixes the segfault for the test case I posted.
Thanks for the report! You are a good dogfooder.
Thanks,
-Stolee
next prev parent reply other threads:[~2018-09-21 14:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 5:22 What's cooking in git.git (Sep 2018, #04; Thu, 20) Junio C Hamano
2018-09-21 14:30 ` Segfault in master due to 4fbcca4eff Ævar Arnfjörð Bjarmason
2018-09-21 14:34 ` Derrick Stolee
2018-09-21 14:40 ` Ævar Arnfjörð Bjarmason
2018-09-21 14:53 ` Derrick Stolee [this message]
2018-09-21 15:55 ` Junio C Hamano
2018-09-21 23:37 ` Ævar Arnfjörð Bjarmason
2018-09-21 23:45 ` Jeff King
2018-09-21 23:49 ` Ævar Arnfjörð Bjarmason
2018-09-21 17:05 ` What's cooking in git.git (Sep 2018, #04; Thu, 20) Johannes Sixt
2018-09-21 17:17 ` Junio C Hamano
2018-09-23 21:39 ` Paul-Sebastian Ungureanu
2018-10-01 19:16 ` René Scharfe
2018-10-01 20:12 ` Jeff King
2018-10-01 21:37 ` René Scharfe
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=5e7e6519-21c1-daff-65a5-7d2ca5e1dbd4@gmail.com \
--to=stolee@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).