From: Jeff Hostetler <git@jeffhostetler.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com, peff@peff.net,
avarab@gmail.com, Jeff Hostetler <jeffhost@microsoft.com>
Subject: Re: [PATCH v3] json_writer: new routines to create data in JSON format
Date: Fri, 23 Mar 2018 15:33:46 -0400 [thread overview]
Message-ID: <6b27b09b-727d-1c3f-c311-5cf6c9bafb4f@jeffhostetler.com> (raw)
In-Reply-To: <20180323171828.GD179915@aiede.svl.corp.google.com>
On 3/23/2018 1:18 PM, Jonathan Nieder wrote:
> git@jeffhostetler.com wrote:
>
>> From: Jeff Hostetler <jeffhost@microsoft.com>
>>
>> Add basic routines to generate data in JSON format.
>>
>> Signed-off-by: Jeff Hostetler <jeffhost@microsoft.com>
>
> If I understand the cover letter correctly, this is a JSON-like
> format, not actual JSON. Am I understanding correctly?
>
> What are the requirements for consuming this output? Will a typical
> JSON library be able to handle it without trouble? If not, is there
> some subset of cases where a typical JSON library is able to handle it
> without trouble?
I'll add text to the commit message and the .h file explaining
the Unicode limitation in the next reroll.
>
> Can you say a little about the motivation here? (I know you already
> put some of that in the cover letter, but since that doesn't become
> part of permanent history, it doesn't help the audience that matters.)
I'll add a note about that to the commit message.
Thanks.
>
> This would also be easier to review if there were an application of it
> in the same series. It's fine to send an RFC like this without such
> an application, but I think we should hold off on merging it until we
> have one. Having an application makes review much easier since we can
> see how the API works in practice, how well the approach fits what
> users need, etc.
That's fine. I'm planning to push up another patch series next week
that builds upon this, so hopefully that will help.
>
> Thanks and hope that helps,
> Jonathan
Thanks,
Jeff
next prev parent reply other threads:[~2018-03-23 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 16:29 [PATCH v3] routines to generate JSON data git
2018-03-23 16:29 ` [PATCH v3] json_writer: new routines to create data in JSON format git
2018-03-23 17:18 ` Jonathan Nieder
2018-03-23 19:33 ` Jeff Hostetler [this message]
2018-03-23 16:41 ` [PATCH v3] routines to generate JSON data Jonathan Nieder
2018-03-23 18:14 ` Ramsay Jones
2018-03-23 19:36 ` 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=6b27b09b-727d-1c3f-c311-5cf6c9bafb4f@jeffhostetler.com \
--to=git@jeffhostetler.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffhost@microsoft.com \
--cc=jrnieder@gmail.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 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).