Re: [PATCH 7/9] Add infrastructure to write revisions in fast-export format

From: Jonathan Nieder <jrnieder@gmail.com>
Date: Jun 24, 2010, 19:36 UTC
Message-ID: <20100624193629.GA2065@burratino>
In-Reply-To: <AANLkTikyjq7HQY1hUTOGF_oBsGDj_jUI-GwDBRdacCzG@mail.gmail.com>

Ramkumar Ramachandra wrote:

> This is like API documentation- should it go into the commit message?
> Maybe put this in a a dedicated repo_tree.txt like trp.h?

Good question. The answer depends on whether we want to keep it maintained.

Since this is not meant to be a general-purpose API, I thought it simplest to document it in the commit message and let future commit messages describe the purpose of future changes. We are not approaching any limit on the length of a commit object, after all.

Jonathan

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