From: git@jeffhostetler.com
To: git@vger.kernel.org
Cc: gitster@pobox.com, peff@peff.net,
Jeff Hostetler <jeffhost@microsoft.com>
Subject: [PATCH v7 0/2] json-writer V7
Date: Tue, 5 Jun 2018 16:33:56 +0000 [thread overview]
Message-ID: <20180605163358.119080-1-git@jeffhostetler.com> (raw)
From: Jeff Hostetler <jeffhost@microsoft.com>
Here is V7 of my json-writer patches. Please replace the existing V5/V6
version of jh/json-writer branch with this one.
This version cleans up the die()-vs-BUG() issue that Duy mentioned recently.
It also fixes a formatting bug when composing empty sub-objects/-arrays.
It also includes a new Python-based test to consume the generated JSON.
I plan to use the json-writer routines in a followup telemetry patch series.
Jeff Hostetler (2):
json_writer: new routines to create data in JSON format
json-writer: t0019: add Python unit test
Makefile | 2 +
json-writer.c | 419 ++++++++++++++++++++++++++++++++
json-writer.h | 113 +++++++++
t/helper/test-json-writer.c | 572 ++++++++++++++++++++++++++++++++++++++++++++
t/t0019-json-writer.sh | 274 +++++++++++++++++++++
t/t0019/parse_json_1.py | 35 +++
6 files changed, 1415 insertions(+)
create mode 100644 json-writer.c
create mode 100644 json-writer.h
create mode 100644 t/helper/test-json-writer.c
create mode 100755 t/t0019-json-writer.sh
create mode 100644 t/t0019/parse_json_1.py
--
2.9.3
next reply other threads:[~2018-06-05 16:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 16:33 git [this message]
2018-06-05 16:33 ` [PATCH v7 1/2] json_writer: new routines to create data in JSON format git
2018-06-05 16:33 ` [PATCH v7 2/2] json-writer: t0019: add Python unit test git
2018-06-06 17:10 ` Todd Zullinger
2018-06-06 21:03 ` Jeff King
2018-06-06 21:11 ` Jeff Hostetler
2018-06-07 0:16 ` Ramsay Jones
2018-06-07 1:49 ` Todd Zullinger
2018-06-07 2:38 ` Jeff King
2018-06-07 2:23 ` Jeff King
2018-06-07 2:49 ` Jeff King
2018-06-07 19:03 ` Ramsay Jones
2018-06-06 21:05 ` Jeff Hostetler
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180605163358.119080-1-git@jeffhostetler.com \
--to=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffhost@microsoft.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.