From: D. Ben Knoble <ben.knoble@gmail.com>
Date: Sun, 17 Aug 2025 21:28:15 GMT
Subject: Re: [RFE] Add JSON output to git log commands
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:
>
> 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