From: Jeff King <peff@peff.net>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: redoste <redoste@redoste.xyz>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Fabian Stelzer <fs@gigacodes.de>,
Elijah Newren <newren@gmail.com>
Subject: Re: [PATCH] ssh signing: don't detach the filename strbuf from key_file tempfile
Date: Sat, 5 Jul 2025 23:13:37 -0400 [thread overview]
Message-ID: <20250706031337.GA3041790@coredump.intra.peff.net> (raw)
In-Reply-To: <aGnDO3HIAQgsRbnJ@fruit.crustytoothpaste.net>
On Sun, Jul 06, 2025 at 12:28:43AM +0000, brian m. carlson wrote:
> On 2025-07-05 at 22:50:43, redoste wrote:
> [...]
> > Since I knew that the Linux kernel changed their documentation to remove
> > the use of "real name", I thought it was more common and didn't relly
> > think about it a lot.
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d4563201f33a022fc0353033d9dfeb1606a88330
> >
> > I'm sorry, I should have read the git documentation more thoroughly.
> >
> > If it's really an issue I don't mind signing off with a different and
> > more distinctive name.
>
> No, I think this is fine. You weren't obligated to explain that and our
> policies should gracefully handle this situation regardless, but given
> what I said before and this context, I think the name you have is fine.
> Git unfortunately has poor support for replacing names and I would't
> want you to have to put your deadname into our history for all of
> eternity.
>
> I'll send a patch to fix the policy.
Ah, I hadn't heard about that change in the kernel. I agree that it
would make sense to loosen our text to match.
Thanks (in advance) for sending that doc update, and for your earlier
comments in the thread. I agreed with everything you wrote there. FWIW,
my personal inclinations lean much more towards allowing privacy and
anonymity, but as a reviewer for the project I wanted to make sure we
were not violating our own policy in a way that would eventually bite us
in a legal sense. The notion of "identifiable but pseudonymous" you
brought up seems like a good middle ground (at least to my layman's
ears).
And thanks redoste for your patch. ;) Sorry if bringing up the signoff
issue caused any hassle (but hopefully it will lead to an improvement to
our docs).
-Peff
next prev parent reply other threads:[~2025-07-06 3:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 23:08 [PATCH] ssh signing: don't detach the filename strbuf from key_file tempfile redoste
2025-07-05 19:21 ` Jeff King
2025-07-05 20:07 ` brian m. carlson
2025-07-05 22:50 ` redoste
2025-07-05 23:04 ` redoste
2025-07-06 0:28 ` brian m. carlson
2025-07-06 3:13 ` Jeff King [this message]
2025-07-06 17:20 ` redoste
2025-07-06 17:14 ` redoste
2025-07-06 17:34 ` [PATCH v2] " redoste
2025-07-06 21:21 ` brian m. carlson
2025-07-07 9:02 ` Patrick Steinhardt
2025-07-07 9:35 ` Phillip Wood
2025-07-07 14:25 ` redoste
2025-07-07 15:26 ` Phillip Wood
2025-07-07 16:22 ` redoste
2025-07-07 16:42 ` Phillip Wood
2025-07-07 18:48 ` [PATCH v3] " redoste
2025-07-07 20:57 ` Junio C Hamano
2025-07-08 6:47 ` Patrick Steinhardt
2025-07-08 13:59 ` Phillip Wood
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=20250706031337.GA3041790@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=fs@gigacodes.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=redoste@redoste.xyz \
--cc=sandals@crustytoothpaste.net \
/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).