Re: [PATCH v4 0/2] rev-list: print additional missing object information

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 5, 2025, 18:29 UTC
Message-ID: <xmqqpljwnt26.fsf@gitster.g>
In-Reply-To: <4peozlz56kmdhziyq6uhsvm4t7atmwtbl7divyuqqb4l64wgom@z3adjdx7v5x2>

Justin Tobler <jltobler@gmail.com> writes:

> wouldn't be sufficient to determine where each record would end. Using
> two NUL bytes next to each other to mark the end of a record would work
> though.

I think we already use that convention elsewhere, and that is why I brought it up as a potential approach to take.

$ 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.