From: Junio C Hamano <gitster@pobox.com>
To: "Troels Thomsen" <troels@thomsen.io>
Cc: "Troels Thomsen via GitGitGadget" <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] receive-pack: fix crash on out-of-namespace symref
Date: Sun, 22 Feb 2026 12:35:46 -0800 [thread overview]
Message-ID: <xmqqcy1wqzx9.fsf@gitster.g> (raw)
In-Reply-To: <ead4041f-bbc3-41ea-8729-9534e69e5e83@app.fastmail.com> (Troels Thomsen's message of "Sun, 22 Feb 2026 08:56:55 +0100")
"Troels Thomsen" <troels@thomsen.io> writes:
> Do you think your original concern could be addressed by adding a note
> to the security section of gitnamespaces?
Not really. Nobody reads documentation, so it would be far more
preferrable to make the default strict, with a documented way to
optionally loosen, than the other way around.
prev parent reply other threads:[~2026-02-22 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-27 15:40 [PATCH] receive-pack: fix crash on out-of-namespace symref Troels Thomsen via GitGitGadget
2025-12-28 14:57 ` Junio C Hamano
2025-12-28 16:26 ` Troels Thomsen
2025-12-30 0:37 ` Junio C Hamano
2026-02-21 17:00 ` Junio C Hamano
2026-02-22 7:56 ` Troels Thomsen
2026-02-22 20:35 ` 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=xmqqcy1wqzx9.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=troels@thomsen.io \
/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