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

Re: [PATCH v2] doc: patch-id: convert to the modern synopsis style

From
Kristoffer Haugsbakk <code@khaugsbakk.name>
Date
Oct 14, 2025, 20:46 UTC
Message-ID
<c9314e08-e0eb-4de4-8f34-a6b4de69e28f@app.fastmail.com>
In-Reply-To
<CAPig+cSQB0HbhY2L1Y4mkbaCMiZTH72AtQ+qRg=Z0U9_ggkcug@mail.gmail.com>
On Mon, Oct 13, 2025, at 18:53, Eric Sunshine wrote:
Show 16 quoted lines
> On Mon, Oct 13, 2025 at 12:28 PM <kristofferhaugsbakk@fastmail.com> wrote:
>> Convert this command documentation to the modern synopsis style based on
>> similar work.[1] Concretely: [...]
>>
>> Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
>> ---
>> diff --git a/Documentation/git-patch-id.adoc b/Documentation/git-patch-id.adoc
>> @@ -7,8 +7,8 @@ git-patch-id - Compute unique ID for a patch
>> ---unstable::
>> +`--unstable`::
>>         Use an "unstable" hash as the patch ID. With this option,
>>         the result produced is compatible with the patch-id value produced
>>         by git 1.9 and older and whitespace is ignored.  Users with pre-existing
>
> Is the mix of "patch ID" and "patch-id" intentional? If so, should
> "patch-id" be wrapped in backticks?

I originally assumed that “patch-id” here meant “patch ID` but now I’m not sure (what was intended).

The way I read it then made me change all of these “patch-id” to “patch ID” for consistency. That’s a future change/topic.

Previous: Eric Sunshine
Message 10 of 10 in “doc: patch-id: convert to the modern synopsis style”
  1. doc: patch-id: convert to the modern synopsis stylekristofferhaugsbakk@fastmail.com, Oct 9, 2025
  2. Jeff KingOct 10, 2025
  3. Kristoffer HaugsbakkOct 13, 2025
  4. Jean-Noël AvilaOct 10, 2025
  5. Kristoffer HaugsbakkOct 13, 2025
  6. Junio C HamanoOct 10, 2025
  7. Kristoffer HaugsbakkOct 13, 2025
  8. doc: patch-id: convert to the modern synopsis stylekristofferhaugsbakk@fastmail.com, Oct 13, 2025
  9. Eric SunshineOct 13, 2025
  10. Kristoffer HaugsbakkOct 14, 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.