git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: exporting git commands in parsable format for constructing language-specific API for git CLI

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 7, 2021, 20:42 UTC
Message-ID
<xmqq4kghzv0w.fsf@gitster.g>
In-Reply-To
<CAJxd1DNB=OGgNkLHg=2TpQxgWKp1dTcg5vvFXG7+2MS0KyXjJA@mail.gmail.com>
ama bamo <pythoncontrol@gmail.com> writes:
> By following the definition of CLI and API; the CLI is human readable
> while the API is machine readable. If we were able to expose CLI
> in a machine-readable format then would it be an API?

Both input and output for Porcelain commands are subject to change to improve the end user experience for humans, which may break scripts that hardcodes the assumption of either the input or the output at one version of Git.

So no, I wouldn't call that an API.
Previous: ama bamo
Message 4 of 4 in “exporting git commands in parsable format for constructing language-specific API for git CLI”
  1. ama bamoMar 27, 2021
  2. Santiago Torres AriasMar 28, 2021
  3. ama bamoApr 7, 2021
  4. Junio C HamanoApr 7, 2021

Read the whole thread, see it on lore, or plain text.

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