Git development
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Elia Pinto <gitter.spiros@gmail.com>
Cc: git@vger.kernel.org,
	"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	"Jeff King" <peff@peff.net>, "Junio C Hamano" <gitster@pobox.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [PATCH v2 4/4] convert: use size_t for text statistics and ident counts
Date: Mon, 2 Nov 2026 12:09:06 +0100	[thread overview]
Message-ID: <auhvUm4VwXyWNhsE@pks.im> (raw)
In-Reply-To: <20261031101619.172770-2-gitter.spiros@gmail.com>

On Sat, Oct 31, 2026 at 11:16:19AM +0100, Elia Pinto wrote:
> On Fri, Oct 30, 2026 at 12:44:40PM +0100, Patrick Steinhardt wrote:
[snip]
> > These paragraphs very much read like AI to me. I would appreciate a
> > human touch, also to demonstrate that a human was involved between us
> > and the AI that tries to understand what was done.
> 
> You're completely right. I used AI tooling to help draft that commit
> message, and it definitely shows. Fair cop.
> 
> To clarify my involvement: I review the code, check the cases, run the
> tests, and take full responsibility for what gets submitted. But the
> wording here missed the mark. For v3 I rewrote the message myself,
> keeping it much shorter, focusing on a single example (lone LFs), and
> dropping the heavy-handed explanations.

Sorry, but is this reply to my ask to proof read what AI generates and
make it sound less AI generated repeating the _exact same thing_ that I
just asked you to change?

To put it bluntly: behaviour like this is what will make me ignore your
patch series altogether going forward. It is frustrating to me, and I
only have limited time to spend on reviews. So I will much rather spend
my own time on patches where I don't feel like I'm talking to a meat
proxy, because I'm a (somewhat) social creature that prefers to talk to
humans.

So please reevaluate what you are doing here.

Patrick

  reply	other threads:[~2026-11-02 11:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 10:16 [PATCH 0/3] use size_t for a few more object and buffer sizes Elia Pinto
2026-10-21 10:16 ` [PATCH 1/3] odb: use size_t for the length of objects to write Elia Pinto
2026-10-21 11:24   ` Patrick Steinhardt
2026-10-21 10:16 ` [PATCH 2/3] diff: use size_t for the allocation size of word-diff buffers Elia Pinto
2026-10-21 11:24   ` Patrick Steinhardt
2026-10-21 10:16 ` [PATCH 3/3] convert: use size_t for buffer sizes Elia Pinto
2026-10-21 11:24   ` Patrick Steinhardt
2026-10-30  9:58 ` [PATCH v2 0/4] use size_t for a few more object and " Elia Pinto
2026-10-30  9:58   ` [PATCH v2 1/4] odb: use size_t for the length of objects to write Elia Pinto
2026-10-30 11:44     ` Patrick Steinhardt
2026-10-31 10:16       ` Elia Pinto
2026-10-30  9:58   ` [PATCH v2 2/4] diff: use size_t for the allocation size of word-diff buffers Elia Pinto
2026-10-30  9:58   ` [PATCH v2 3/4] convert: use size_t for buffer sizes Elia Pinto
2026-10-30  9:58   ` [PATCH v2 4/4] convert: use size_t for text statistics and ident counts Elia Pinto
2026-10-30 11:44     ` Patrick Steinhardt
2026-10-31 10:16       ` Elia Pinto
2026-11-02 11:09         ` Patrick Steinhardt [this message]
2026-11-02 20:16           ` Junio C Hamano
2026-10-31 10:16   ` [PATCH v3 0/4] use size_t for a few more object and buffer sizes Elia Pinto
2026-10-31 10:16     ` [PATCH v3 1/4] odb: use size_t for the length of objects to write Elia Pinto
2026-10-31 10:16     ` [PATCH v3 2/4] diff: use size_t for the allocation size of word-diff buffers Elia Pinto
2026-10-31 10:16     ` [PATCH v3 3/4] convert: use size_t for buffer sizes Elia Pinto
2026-10-31 10:16     ` [PATCH v3 4/4] convert: use size_t for text statistics and ident counts Elia Pinto

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=auhvUm4VwXyWNhsE@pks.im \
    --to=ps@pks.im \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=gitter.spiros@gmail.com \
    --cc=peff@peff.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