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

Re: [PATCH 1/5] doc: convert git-bisect to synopsis style

From
Junio C Hamano <gitster@pobox.com>
Date
May 18, 2026, 00:26 UTC
Message-ID
<xmqq4ik5d0le.fsf@gitster.g>
In-Reply-To
<dca7f192f1e5cdfb57682feace0a4b3a10204376.1779049615.git.gitgitgadget@gmail.com>
"Jean-Noël Avila via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 5 quoted lines
> From: =?UTF-8?q?Jean-No=C3=ABl=20Avila?= <jn.avila@free.fr>
>
> Convert Documentation/git-bisect.adoc to the modern synopsis style.
>
> - Replace [verse] with [synopsis] in the SYNOPSIS block
This was expected.
> - Remove single quotes around command names in the synopsis
> - Use backticks for inline commands, options, refs, and special values
> - Apply [synopsis] attribute to in-body command-form code blocks

This is very much unexpected. I think everybody thought [synopsis] was invented to be used for the SYNOPSIS section at the beginning of each manual page, and ...

Show 12 quoted lines
>  SYNOPSIS
>  --------
> -[verse]
> -'git bisect' start [--term-(bad|new)=<term-new> --term-(good|old)=<term-old>]
> -		   [--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<pathspec>...]
> ...
> -'git bisect' help
> +[synopsis]
> +git bisect start [--term-(bad|new)=<term-new> --term-(good|old)=<term-old>]
> +		 [--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<pathspec>...]
> ...
> +git bisect help

... a change like this is very much expected and understandable, but new appearances of [synonsis] in places like:

> +[synopsis]
>  ------------------------------------------------
>  $ git bisect reset <commit>
>  ------------------------------------------------
and
> +[synopsis]
>  ------------------------------------------------
>  git bisect old [<rev>]
>  ------------------------------------------------

were a bit surprising and confusing. They are not exactly command syntax definitions (which is the SYNOPSIS section is about), but examples of usage. The one with '$' command line prompt feels particularly confusing, as the prompt is not something that the end-user gives, unlike what we write in the synopsis section.

Other than that, this is quite exciting.
Previous: Jean-Noël Avila via GitGitGadgetNext: Junio C Hamano
Message 3 of 17 in “doc: convert another batch of files to synopsis style”
  1. 0/5 doc: convert another batch of files to synopsis styleJean-Noël Avila via GitGitGadget, May 17, 2026
  2. 1/5 doc: convert git-bisect to synopsis styleJean-Noël Avila via GitGitGadget, May 17, 2026
  3. Junio C HamanoMay 18, 2026
  4. Junio C HamanoMay 18, 2026
  5. Jean-Noël AVILAMay 19, 2026
  6. Jean-Noël AVILAMay 19, 2026
  7. 2/5 doc: convert git-grep synopsis and options to new styleJean-Noël Avila via GitGitGadget, May 17, 2026
  8. 3/5 doc: convert git-am synopsis and options to new styleJean-Noël Avila via GitGitGadget, May 17, 2026
  9. 4/5 doc: convert git-apply synopsis and options to new styleJean-Noël Avila via GitGitGadget, May 17, 2026
  10. 5/5 doc: convert git-imap-send synopsis and options to new styleJean-Noël Avila via GitGitGadget, May 17, 2026
  11. 0/6 doc: convert another batch of files to synopsis styleJean-Noël Avila via GitGitGadget, May 25, 2026
  12. 1/6 doc: convert git-bisect to synopsis styleJean-Noël Avila via GitGitGadget, May 25, 2026
  13. 2/6 doc: git bisect: clarify the usage of the synopsis vs actual commandJean-Noël Avila via GitGitGadget, May 25, 2026
  14. 3/6 doc: convert git-grep synopsis and options to new styleJean-Noël Avila via GitGitGadget, May 25, 2026
  15. 4/6 doc: convert git-am synopsis and options to new styleJean-Noël Avila via GitGitGadget, May 25, 2026
  16. 5/6 doc: convert git-apply synopsis and options to new styleJean-Noël Avila via GitGitGadget, May 25, 2026
  17. 6/6 doc: convert git-imap-send synopsis and options to new styleJean-Noël Avila via GitGitGadget, May 25, 2026

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.