From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: git@jeffhostetler.com, git@vger.kernel.org
Cc: gitster@pobox.com, peff@peff.net, l.s.r@web.de, wink@saville.com,
Jeff Hostetler <jeffhost@microsoft.com>
Subject: Re: [PATCH v4] json_writer: new routines to create data in JSON format
Date: Tue, 27 Mar 2018 04:18:21 +0100 [thread overview]
Message-ID: <ce076d5e-f30f-006e-a25e-ff1a900562bf@ramsayjones.plus.com> (raw)
In-Reply-To: <20180326143136.47116-2-git@jeffhostetler.com>
On 26/03/18 15:31, git@jeffhostetler.com wrote:
> From: Jeff Hostetler <jeffhost@microsoft.com>
>
> Add a series of jw_ routines and "struct json_writer" structure to compose
> JSON data. The resulting string data can then be output by commands wanting
> to support a JSON output format.
>
> The json-writer routines can be used to generate structured data in a
> JSON-like format. We say "JSON-like" because we do not enforce the Unicode
> (usually UTF-8) requirement on string fields. Internally, Git does not
> necessarily have Unicode/UTF-8 data for most fields, so it is currently
> unclear the best way to enforce that requirement. For example, on Linx
> pathnames can contain arbitrary 8-bit character data, so a command like
> "status" would not know how to encode the reported pathnames. We may want
> to revisit this (or double encode such strings) in the future.
>
> The initial use for the json-writer routines is for generating telemetry
> data for executed Git commands. Later, we may want to use them in other
> commands, such as status.
>
> Helped-by: René Scharfe <l.s.r@web.de>
> Helped-by: Wink Saville <wink@saville.com>
> Helped-by: Ramsay Jones <ramsay@ramsayjones.plus.com>
> Signed-off-by: Jeff Hostetler <jeffhost@microsoft.com>
> ---
> Makefile | 2 +
> json-writer.c | 395 +++++++++++++++++++++++++++++
> json-writer.h | 92 +++++++
> t/helper/test-json-writer.c | 590 ++++++++++++++++++++++++++++++++++++++++++++
> t/t0019-json-writer.sh | 253 +++++++++++++++++++
> 5 files changed, 1332 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
>
[snip]
Thanks, this version fixes all issues I had (with the compilation
and sparse warnings).
[Was using UINT64_C(0xffffffffffffffff) a problem on windows?]
ATB,
Ramsay Jones
next prev parent reply other threads:[~2018-03-27 3:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 14:31 [PATCH v4] routines to generate JSON data git
2018-03-26 14:31 ` [PATCH v4] json_writer: new routines to create data in JSON format git
2018-03-27 3:18 ` Ramsay Jones [this message]
2018-03-27 10:28 ` Jeff Hostetler
2018-03-27 15:45 ` Ramsay Jones
2018-03-27 17:14 ` Jeff Hostetler
2018-03-27 17:43 ` Wink Saville
2018-03-27 18:00 ` Randall S. Becker
2018-03-28 5:22 ` Junio C Hamano
2018-03-27 18:05 ` Ramsay Jones
2018-03-28 1:22 ` Junio C Hamano
2018-06-02 4:41 ` Duy Nguyen
2018-06-02 5:13 ` Jeff King
2018-06-04 9:41 ` 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=ce076d5e-f30f-006e-a25e-ff1a900562bf@ramsayjones.plus.com \
--to=ramsay@ramsayjones.plus.com \
--cc=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=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.
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 NNTP newsgroup(s).