From: git@jeffhostetler.com
To: git@vger.kernel.org
Cc: gitster@pobox.com, peff@peff.net, l.s.r@web.de, wink@saville.com,
ramsay@ramsayjones.plus.com,
Jeff Hostetler <jeffhost@microsoft.com>
Subject: [PATCH v5] routines to generate JSON data
Date: Tue, 27 Mar 2018 21:02:32 +0000 [thread overview]
Message-ID: <20180327210233.29076-1-git@jeffhostetler.com> (raw)
From: Jeff Hostetler <jeffhost@microsoft.com>
This is version 5 of my JSON data format routines.
This version address the uint64_t vs intmax_t formatting issues
that were discussed on the mailing list. I removed the jw_*_int()
and jw_*_uint64() routines and replaced them with a single
jw_*_intmax() routine.
Also added a jw_release() routine similar to strbuf_release()
and fixed the indentation of sub-array when pretty printing is
enabled.
The following PR includes my WIP telemetry changes that build
upon the json-writer routines and demonstrates how they might
be used. The first commit in this PR is this patch.
https://github.com/jeffhostetler/git/pull/11
Jeff Hostetler (1):
json_writer: new routines to create data in JSON format
Makefile | 2 +
json-writer.c | 394 ++++++++++++++++++++++++++++++
json-writer.h | 91 +++++++
t/helper/test-json-writer.c | 572 ++++++++++++++++++++++++++++++++++++++++++++
t/t0019-json-writer.sh | 253 ++++++++++++++++++++
5 files changed, 1312 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
--
2.9.3
next reply other threads:[~2018-03-27 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 21:02 git [this message]
2018-03-27 21:02 ` [PATCH v5] json_writer: new routines to create data in JSON format git
2018-03-27 22:03 ` Wink Saville
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
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 \
--in-reply-to=20180327210233.29076-1-git@jeffhostetler.com \
--to=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffhost@microsoft.com \
--cc=l.s.r@web.de \
--cc=peff@peff.net \
--cc=ramsay@ramsayjones.plus.com \
--cc=wink@saville.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).