Re: [PATCH 0/4] repo: add support for path-related fields

From: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
Date: Mar 1, 2026, 19:49 UTC
Message-ID: <12F0E36B-6F42-494A-B985-E41C9C4BF92F@gmail.com>
In-Reply-To: <CA+rGoLdTc2caDUsQedpegL+T4MqwwiA62uuDSFSawAT5vcPvWQ@mail.gmail.com>

> Option 1 feels like the cleanest approach.
> Even though it means git-repo-info can't return both a relative and
> absolute path in the exact same call, it keeps the API highly predictable
> for scripting without bloating the key namespace (which Option 3 would do).

Yeah. I think that in the future most of them will be path.*, and 3 would double them...

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