From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: Patrick Steinhardt <ps@pks.im>,
Harald Nordgren <haraldnordgren@gmail.com>,
Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
git@vger.kernel.org, "D. Ben Knoble" <ben.knoble@gmail.com>,
GGG <gitgitgadget@gmail.com>
Subject: Re: [PATCH v3] object-name: explain why <rev>~N fails in a shallow clone
Date: Mon, 02 Nov 2026 10:55:06 -0800 [thread overview]
Message-ID: <xmqqpkwnhxmd.fsf@gitster.g> (raw)
In-Reply-To: <50c6229a-336e-4488-9289-183f5ffc47cd@gmail.com> (Phillip Wood's message of "Mon, 2 Nov 2026 14:36:39 +0000")
Phillip Wood <phillip.wood123@gmail.com> writes:
> something like "for every three patch series you submit you should
> provide an in-depth review of one series from another contributor". I'm
> not sure how well that would work (I seem to remember reading PostgreSQL
> tried something similar and ended up abandoning it) but it might be
> worth a try.
Hmph, I do not know if you want a "contributor" who throws too many
AI slop at us to contaminate discussion threads on others' patches
with their AI generated "reviews" in the first place, though.
next prev parent reply other threads:[~2026-11-02 18:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 9:53 [PATCH] object-name: explain why <ref>~N fails in a shallow clone Harald Nordgren via GitGitGadget
2026-09-20 21:59 ` D. Ben Knoble
2026-09-21 16:50 ` Junio C Hamano
2026-09-21 22:17 ` Harald Nordgren
2026-09-21 23:00 ` Junio C Hamano
2026-09-22 13:38 ` [PATCH v2] shallow: advise when a walk stops at a shallow boundary Harald Nordgren via GitGitGadget
2026-09-22 21:20 ` Junio C Hamano
2026-09-23 18:55 ` [PATCH v3] object-name: explain why <rev>~N fails in a shallow clone Harald Nordgren via GitGitGadget
2026-11-02 9:21 ` Junio C Hamano
2026-11-02 10:06 ` Harald Nordgren
2026-11-02 11:01 ` Kristoffer Haugsbakk
2026-11-02 11:07 ` Harald Nordgren
2026-11-02 12:24 ` Patrick Steinhardt
2026-11-02 12:44 ` Kristoffer Haugsbakk
2026-11-02 14:07 ` Harald Nordgren
2026-11-02 14:31 ` Patrick Steinhardt
2026-11-02 14:48 ` Harald Nordgren
2026-11-02 14:36 ` Phillip Wood
2026-11-02 14:52 ` Harald Nordgren
2026-11-02 18:55 ` Junio C Hamano [this message]
2026-11-02 18:40 ` Junio C Hamano
2026-11-02 12:34 ` Kristoffer Haugsbakk
2026-11-02 14:10 ` Harald Nordgren
2026-11-02 14:33 ` Patrick Steinhardt
2026-11-02 18:35 ` Junio C Hamano
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=xmqqpkwnhxmd.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=haraldnordgren@gmail.com \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=phillip.wood123@gmail.com \
--cc=ps@pks.im \
/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