From: Junio C Hamano <gitster@pobox.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: Yuvraj Singh Chauhan <ysinghcin@gmail.com>,
git@vger.kernel.org, christian.couder@gmail.com,
stolee@gmail.com
Subject: Re: [PATCH v1] path-walk: fix NULL pointer dereference in error message
Date: Fri, 20 Mar 2026 10:08:13 -0700 [thread overview]
Message-ID: <xmqqy0jme8ea.fsf@gitster.g> (raw)
In-Reply-To: <CALnO6CDnwYaAPhp67kaYWtV48ULjWAR6ks1khVXmSs1oWUbRDQ@mail.gmail.com> (D. Ben Knoble's message of "Fri, 20 Mar 2026 11:16:48 -0400")
"D. Ben Knoble" <ben.knoble@gmail.com> writes:
> You mentioned git-backfill with a tree missing from the local odb; do
> you have a short reproduction script or test-case?
Interesting thing to ask. THe code looks correct, though.
next prev parent reply other threads:[~2026-03-20 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 11:48 [PATCH v1] path-walk: fix NULL pointer dereference in error message Yuvraj Singh Chauhan
2026-03-20 15:16 ` D. Ben Knoble
2026-03-20 16:14 ` Derrick Stolee
2026-03-23 9:45 ` Yuvraj Singh Chauhan
2026-03-20 17:08 ` Junio C Hamano [this message]
2026-03-20 18:54 ` René Scharfe
2026-03-22 14:21 ` D. Ben Knoble
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=xmqqy0jme8ea.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=stolee@gmail.com \
--cc=ysinghcin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.