Re: Pain points in Git's patch flow

From: dwh@linuxprogrammer.org <dwh@linuxprogrammer.org>
Date: May 8, 2021, 02:10 UTC
Message-ID: <20210508021011.GG3986@localhost>
In-Reply-To: <20210419220013.mguw4l5644r2c7gj@nitro.local>

On 19.04.2021 18:00, Konstantin Ryabitsev wrote:

>I view email as merely one way of exchanging RFC2822-formatted messages.
>There are others and RFC2822 is robust enough to serve as a good standard
>base that allows both free-form and structured content, including mixed.

+1 on RFC2822 as universal message format. It is simple, easy to understand, trivial to manipulate in any programming language and widely supported. Standard file formats, along with standard protocols, both without "proprietary extensinos" is the key to maintaining decentralization and avoiding siloing of data and users.

Cheers! Dave

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