From: Jeff King <email@example.com>
To: Martin Langhoff <firstname.lastname@example.org>
Cc: Git Mailing List <email@example.com>
Subject: Re: Structured (ie: json) output for query commands?
Date: Wed, 30 Jun 2021 13:59:43 -0400 [thread overview]
Message-ID: <YNyxD4qAHmbluNRe@coredump.intra.peff.net> (raw)
On Wed, Jun 30, 2021 at 01:00:24PM -0400, Martin Langhoff wrote:
> I'm used to automating git by parsing stuff in Unix shell style. But
> the golden days that gave us Perl are well behind us.
> Before I write (unreliable, leaky, likely buggy) text parsing bits one
> more time, has git grown formatted output? I'm aware of fmt and
> friends, I'm thinking of something that handles escaping, nested data
> structures, etc.
> Something like "git shortlog --json".
> Have there been discussions? Patches? (I don't spot anything in what's cooking).
It's been discussed off-and-on over the years, but I don't think
anybody's actively working on it.
The trace2 facility has some json output. That's probably not helpful
for what you're doing, but it does mean we have basic json output
One complication we faced is that a lot of Git's data is bag-of-bytes,
not utf8. And json technically requires utf8. I don't remember if we
simply fudged that and output possibly non-utf8 sequences, or if we
actually encode them.
next prev parent reply other threads:[~2021-06-30 17:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACPiFC++fG-WL8uvTkiydf3wD8TY6dStVpuLcKA9cX_EnwoHGA@mail.gmail.com>
2021-06-30 17:00 ` Structured (ie: json) output for query commands? Martin Langhoff
2021-06-30 17:59 ` Jeff King [this message]
2021-06-30 18:20 ` Martin Langhoff
2021-07-01 15:47 ` Jeff King
2021-06-30 20:19 ` brian m. carlson
2021-06-30 23:27 ` Martin Langhoff
2021-07-01 16:00 ` Jeff King
2021-07-01 21:18 ` brian m. carlson
2021-07-01 21:48 ` Jeff King
2021-07-02 13:13 ` Ævar Arnfjörð Bjarmason
2021-07-01 8:18 ` Han-Wen Nienhuys
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).