git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [GSoC PATCH v3 0/2] json-writer: describe the jw_* functions

From
Junio C Hamano <gitster@pobox.com>
Date
May 16, 2025, 16:42 UTC
Message-ID
<xmqq7c2gwlqf.fsf@gitster.g>
In-Reply-To
<CAOLa=ZSH4CUdAUOT7H4B+2dwgfx22wJxxjt0SqPavAnEsdkHMA@mail.gmail.com>
Karthik Nayak <karthik.188@gmail.com> writes:
Show 9 quoted lines
> Lucas Seiki Oshiro <lucasseikioshiro@gmail.com> writes:
>
>> Hello, again!
>>
>> In this v3 I did some minor adjustments based on the review of v2
>> (https://lore.kernel.org/git/20250512020935.73140-1-lucasseikioshiro@gmail.com/).
>>
>
> This version looks good to me, thanks for the update.
Yup, the result reads very well.  Thanks, all.
> I do have some general suggestions (not requirements):
> - It would be nice if these patch versions were inlined with the
>   previous ones. Makes it easier to compare versions while reviewing.
"git send-email --in-reply-to=..." is a good tool to use.
> - Perhaps include a range-diff to make it easier to review the changes
>   in the new version compared to the last one.

Here, "git format-patch --range-diff=..." can help when preparing the patches to be sent.

> I can totally recommend b4 (https://b4.docs.kernel.org/en/latest/), it
> helps manage both of the points I mentioned :)
... and more, by helping on the receiving end, too ;-).
Previous: Karthik Nayak
Message 5 of 5 in “json-writer: describe the jw_* functions”
  1. 0/2 json-writer: describe the jw_* functionsLucas Seiki Oshiro, May 16, 2025
  2. 1/2 json-writer: add docstrings to jw_* functionsLucas Seiki Oshiro, May 16, 2025
  3. 2/2 json-writer: describe the usage of jw_* functionsLucas Seiki Oshiro, May 16, 2025
  4. Karthik NayakMay 16, 2025
  5. Junio C HamanoMay 16, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.