From: Ben Zanin <bzanin@gmail.com>
To: Mike Lodispoto <mike@lodispoto.com>, git@vger.kernel.org
Subject: Re: Shared bare repository dubious ownership error after 2.40.1-r0
Date: Thu, 18 Jul 2024 11:00:53 -0400 [thread overview]
Message-ID: <87wmliycbe.fsf@gmail.com> (raw)
In-Reply-To: <dd703bdc-f485-4162-92a5-fd2828b69604@lodispoto.com> (Mike Lodispoto's message of "Wed, 10 Jul 2024 18:16:50 -0500")
Mike,
It's a long thread that began with the proposal for a new feature, but
there is some valuable discussion midway down about mitigations that are
already in place for the symptom you're describing, and some good
analysis about the tradeoffs of exercising each one:
https://lore.kernel.org/git/20240626123358.420292-1-flo@geekplace.eu/t/
--
Ben
prev parent reply other threads:[~2024-07-18 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 23:16 Shared bare repository dubious ownership error after 2.40.1-r0 Mike Lodispoto
2024-07-18 4:24 ` Colin Stagner
2024-07-18 15:00 ` Ben Zanin [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=87wmliycbe.fsf@gmail.com \
--to=bzanin@gmail.com \
--cc=git@vger.kernel.org \
--cc=mike@lodispoto.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).