From: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, ps@pks.im, karthik.188@gmail.com,
Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
Subject: [GSoC PATCH v2 0/2] json-writer: describe the jw_* functions
Date: Sun, 11 May 2025 23:09:33 -0300 [thread overview]
Message-ID: <20250512020935.73140-1-lucasseikioshiro@gmail.com> (raw)
Hi!
Given that my GSoC project will need the json-writer module for serializing
JSON data, I studied this module and I thought it would be a nice contribution
to make it a little more clear on how to use it. This will be helpful for me and
I hope that it will also be for anyone who want to write JSON inside Git.
The main difference in this v2 is the second commit which provides an
overview on how to use the functions of this module, telling which one should
be used for each use case. Perhaps only this usage overview is enough, but I'm
open for suggestions!
PS: this is the first patchset that I'm sending after being approved in GSoC, so
this is also the first one with Mentored-by :-)
Lucas Seiki Oshiro (2):
json-writer: add docstrings to jw_* functions
json-writer: describe the usage of jw_* functions
json-writer.h | 161 ++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 161 insertions(+)
--
2.39.5 (Apple Git-154)
next reply other threads:[~2025-05-12 2:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 2:09 Lucas Seiki Oshiro [this message]
2025-05-12 2:09 ` [GSoC PATCH v2 1/2] json-writer: add docstrings to jw_* functions Lucas Seiki Oshiro
2025-05-12 8:50 ` Patrick Steinhardt
2025-05-13 22:05 ` Lucas Seiki Oshiro
2025-05-14 2:41 ` Patrick Steinhardt
2025-05-12 9:36 ` Karthik Nayak
2025-05-12 2:09 ` [GSoC PATCH v2 2/2] json-writer: describe the usage of " Lucas Seiki Oshiro
2025-05-12 8:50 ` Patrick Steinhardt
2025-05-12 9:41 ` Karthik Nayak
2025-05-13 22:22 ` Lucas Seiki Oshiro
2025-05-14 2:40 ` Patrick Steinhardt
2025-05-12 8:49 ` [GSoC PATCH v2 0/2] json-writer: describe the " Karthik Nayak
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=20250512020935.73140-1-lucasseikioshiro@gmail.com \
--to=lucasseikioshiro@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=karthik.188@gmail.com \
--cc=ps@pks.im \
/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).