From: "Carlisle T. Hamlin" <hamlin.carlisle@gmx.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Sphinx <sphinx9692@gmail.com>, git@vger.kernel.org
Subject: Re: Question: behavior when reverting a commit from a shallow clone
Date: Mon, 5 Oct 2026 11:10:20 -0700 [thread overview]
Message-ID: <593528e2-bac3-4d9d-8374-be30e97b0028@gmx.com> (raw)
In-Reply-To: <asNKYAHSWJkFkhNn@pks.im>
[-- Attachment #1.1.1: Type: text/plain, Size: 1248 bytes --]
On 10/4/26 11:57 PM, Patrick Steinhardt wrote:
>> You know, it seems to me that it should be reasonable for Git to assume that
>> someone with the wherewithal to set up and operate a git repository (or at
>> the very least operate one that someone else set up) knows enough to
>> understand what's going to happen if they obliterate the only commit in
>> their tree.
>>
>> There really is only *so* much holding of the hand I think we should be
>> expected to perform before it's not only insulting to the project
>> developers, but also to the *user*.
>>
>> My two cents. I know folk use Git for all sorts of stuff. Just, maybe... the
>> sort of person who would be surprised catastrophically by this behaviour...
>> well... shouldn't.
>
> There really is no need to be this adversarial to a simple question like
> from the author. We want to be a welcoming community, and replies like
> this are the exact opposite and will drive people away.
My apologies; I didn't realize I was coming across as adversarial.
Also, I stand corrected - other replies to this question indicate that
we *are, indeed* prepared to perform this level of hand holding. I
fundamentally misunderstood the project's stance in this regard.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7951 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]
next prev parent reply other threads:[~2026-10-05 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 8:54 Question: behavior when reverting a commit from a shallow clone Sphinx
2026-10-03 19:41 ` Carlisle T. Hamlin
2026-10-05 6:57 ` Patrick Steinhardt
2026-10-05 18:10 ` Carlisle T. Hamlin [this message]
2026-10-05 6:57 ` Patrick Steinhardt
2026-10-05 10:41 ` Matt Hunter
2026-10-05 16:38 ` Junio C Hamano
[not found] ` <CALfz8QzymKxvzYGWLwdtzERDm1apa8ebZEVyLne18hpTaB=D0g@mail.gmail.com>
2026-10-05 17:35 ` Sphinx
2026-10-06 15:54 ` Junio C Hamano
2026-10-09 17:34 ` Sphinx
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=593528e2-bac3-4d9d-8374-be30e97b0028@gmx.com \
--to=hamlin.carlisle@gmx.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
--cc=sphinx9692@gmail.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