Re: What's cooking in git.git (Apr 2013, #05; Mon, 15)

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 17, 2013, 04:44 UTC
Message-ID: <7vy5chhik6.fsf@alter.siamese.dyndns.org>
In-Reply-To: <CABURp0qGYG4T+t36=Us328YdLzy9KjBOWot2gSOk=FgCRUCLnQ@mail.gmail.com>

Phil Hord <phil.hord@gmail.com> writes:

Show 9 quoted lines

> ...  Almost every time I bisect a regression
> in git.git, I find the commit message tells me exactly why the commit
> did what it did and what the expected result was.  I find this to be
> amazingly useful.
> ...
> Of course, 99% of the commit messages may never be useful to me or
> anyone else.  But we do not eschew them altogether.  The 1% I have to
> rely on are nearly always helpful and clear, and that is the part I
> care about.

It is nice to be appreciated for our efforts by somebody every once in a while ;-)

Thanks.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.