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

Re: [RFE] Add JSON output to git log commands

From
D. Ben Knoble <ben.knoble@gmail.com>
Date
Aug 17, 2025, 21:28 UTC
Message-ID
<CALnO6CAkTt0brPbnKDu9rOAHeLRtk2hm3xJT5+HvZOfHSL-Szg@mail.gmail.com>
In-Reply-To
<67621563-9441-4ae9-a23b-51af7d3ce666@app.fastmail.com>

On Sun, Aug 17, 2025 at 5:09 PM Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com> wrote:

Show 5 quoted lines
>
> On Sun, Aug 17, 2025, at 22:17, Ron Ziroby Romero wrote:
> > I would like to add JSON output to the git log command.
>
> Previously: https://lore.kernel.org/git/CAGW8g7=21pPAgCixjpayEvmw_ns-hcB4e59NP476TKtCRXHPXQ@mail.gmail.com/

In particular, I would guess that deciding how to handle "raw bytes" (e.g., paths that are not necessarily UTF-8 strings) is important. JSON uses Unicode characters:

     A string is a sequence of zero or more Unicode characters,
wrapped in double quotes, using backslash escapes. A character is
represented as a single character string. A string is very much like a
C or Java string.
https://www.json.org/json-en.html

(even though the railroad diagram says "codepoints"; I find the whole thing a bit muddy—what exactly is representable in JSON strings?

    Excepting a few encoding details, that completely describes the language.
??? which details?)
-- 
D. Ben Knoble
Previous: Kristoffer HaugsbakkNext: brian m. carlson
Message 3 of 5 in “[RFE] Add JSON output to git log commands”
  1. Ron Ziroby RomeroAug 17, 2025
  2. Kristoffer HaugsbakkAug 17, 2025
  3. D. Ben KnobleAug 17, 2025
  4. brian m. carlsonAug 17, 2025
  5. Junio C HamanoAug 17, 2025

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.