From: Patrick Steinhardt <ps@pks.im>
To: Harald Nordgren <haraldnordgren@gmail.com>
Cc: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
Junio C Hamano <gitster@pobox.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, 2 Nov 2026 15:33:33 +0100 [thread overview]
Message-ID: <auifPbwjQgbIQzzK@pks.im> (raw)
In-Reply-To: <CAHwyqnVMb1BtJ0Eb3HqQx9SNyB9oWkhC7OH2_j=xZSiuwreK1w@mail.gmail.com>
On Mon, Nov 02, 2026 at 03:10:56PM +0100, Harald Nordgren wrote:
> > I’m not much of a C programmer.
>
> I'm quite taken aback by this.
>
> Is the Git code so sacred that even the reviewers are not in a
> position to review? :D
There are other ways in which people can contribute, e.g. by
contributing documentation. Not everyone contributing to Git is a
developer -- I'd argue we could in fact use way more non-developer
contributions.
Patrick
next prev parent reply other threads:[~2026-11-02 14:33 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
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 [this message]
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=auifPbwjQgbIQzzK@pks.im \
--to=ps@pks.im \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=haraldnordgren@gmail.com \
--cc=kristofferhaugsbakk@fastmail.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