From: Junio C Hamano Date: Mon, 18 May 2026 00:26:37 GMT Subject: Re: [PATCH 1/5] doc: convert git-bisect to synopsis style Message-ID: In-Reply-To: "Jean-Noël Avila via GitGitGadget" writes: > From: =?UTF-8?q?Jean-No=C3=ABl=20Avila?= > > 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 ... > SYNOPSIS > -------- > -[verse] > -'git bisect' start [--term-(bad|new)= --term-(good|old)=] > - [--no-checkout] [--first-parent] [ [...]] [--] [...] > ... > -'git bisect' help > +[synopsis] > +git bisect start [--term-(bad|new)= --term-(good|old)=] > + [--no-checkout] [--first-parent] [ [...]] [--] [...] > ... > +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 > ------------------------------------------------ and > +[synopsis] > ------------------------------------------------ > git bisect old [] > ------------------------------------------------ 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.