Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] sparse-index: avoid crash on intent-to-add entry outside the cone
Date: Fri, 31 Jul 2026 08:56:46 -0700	[thread overview]
Message-ID: <xmqqtspfcfup.fsf@gitster.g> (raw)
In-Reply-To: <e4cce4e2-4287-4e1a-8833-d37ee48ff7d6@gmail.com> (Derrick Stolee's message of "Fri, 31 Jul 2026 09:23:41 -0400")

Derrick Stolee <stolee@gmail.com> writes:

>> OK.  That is an easy and safe cop-out that is much better than segfaulting.
>> 
>> Shall we mark the topic for 'next'?
> Thanks for taking a look. yes, this should be a pretty safe change that
> can merge.

Thanks.

      reply	other threads:[~2026-07-31 15:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 13:50 [PATCH] sparse-index: avoid crash on intent-to-add entry outside the cone Derrick Stolee via GitGitGadget
2026-07-29 21:51 ` Junio C Hamano
2026-07-31 13:23   ` Derrick Stolee
2026-07-31 15:56     ` Junio C Hamano [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=xmqqtspfcfup.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=stolee@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