Re: Request for detailed documentation of git pack protocol

From: A Large Angry SCM <gitzilla@gmail.com>
Date: May 15, 2009, 00:58 UTC
Message-ID: <4A0CBE35.6030004@gmail.com>
In-Reply-To: <200905141701.41212.jnareb@gmail.com>

Jakub Narebski wrote:

Show 5 quoted lines

> I don't think RFC _process_ is something to worry about; in the future
> perhaps (just like Atom Publishing protocol was submitted to IETF).
> I was thinking about _format_ used in RFC (BNF-like specification,
> specific semantic for 'MUST' etc. like in RFC2119). Although any format
> (more or less formal) would be better that none.

Standardese, the peculiar dialect and formalism employed by RFC authors, is not difficult to master. The difficult part is writing the prose that's an _unambiguous_ description of the protocol you're attempting to document. There's even a tool, xml2rfc, that will do the formatting for you.

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