From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
Git mailing list <git@vger.kernel.org>,
Patrick Steinhardt <ps@pks.im>,
Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Subject: Re: [PATCH v3] builtin/history: unuse the commit buffer after use
Date: Thu, 10 Sep 2026 09:20:40 -0700 [thread overview]
Message-ID: <xmqqv78df57r.fsf@gitster.g> (raw)
In-Reply-To: <20260910160254.GB251185@coredump.intra.peff.net> (Jeff King's message of "Thu, 10 Sep 2026 12:02:54 -0400")
Jeff King <peff@peff.net> writes:
> I'm not suggesting a v3 with this wording, as I think there are
> diminishing returns to polishing commit messages forever. Mostly just
> food for thought for future patches. :)
I obviously agree. I wonder what my recent favorite prompt given to
a nearby LLM, "State the same thing with 1/N number of words"
followed by the proposed commit log message that I found too long to
read, would produce for the v3 message.
I'd use N=8~10 for this one ;-)
next prev parent reply other threads:[~2026-09-10 16:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-14 14:15 [PATCH] builtin/history: unuse the commit buffer after use Kaartic Sivaraam
2026-06-15 9:48 ` Patrick Steinhardt
2026-06-15 17:29 ` Jeff King
2026-06-16 5:45 ` Patrick Steinhardt
2026-06-30 3:45 ` Kaartic Sivaraam
2026-06-30 5:26 ` Jeff King
2026-06-30 3:43 ` Kaartic Sivaraam
2026-06-30 5:38 ` Jeff King
2026-06-30 5:50 ` Jeff King
2026-06-30 6:44 ` Jeff King
2026-09-10 11:39 ` [PATCH v2] " Kaartic Sivaraam
2026-09-10 13:36 ` Junio C Hamano
2026-09-10 15:00 ` [PATCH v3] " Kaartic Sivaraam
2026-09-10 16:02 ` Jeff King
2026-09-10 16:20 ` Junio C Hamano [this message]
2026-09-10 16:37 ` Kaartic Sivaraam
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=xmqqv78df57r.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@gmail.com \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=peff@peff.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.