Re: [PATCH v5 3/9] trailer: prepare to expose functions as part of API

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 29, 2024, 23:21 UTC
Message-ID: <xmqqedcuc0w3.fsf@gitster.g>
In-Reply-To: <owlyttlq529h.fsf@fine.c.googlers.com>

Linus Arver <linusa@google.com> writes:

Show 8 quoted lines

>> Nit: this patch and the next one will become commits, so perhaps:
>>
>> s/In the next patch/In a following commit/
>
> TBH I've always wondered whether "patch" or "commit" matters --- I've
> seen examples of patch series that referred to "commits" instead of
> "patches", and vice versa. I was hoping to hear an opinion on this, so
> I'm happy to see (and apply) your suggestion. Thanks.

I think it is just fine to use either; sticking to one you pick consistently in the same series would have value. If you prefer commit, then fine. If you like patch, that's fine too.

$ 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.