From: Jean-Noël AVILA <jn.avila@free.fr>
Date: Sun, 01 Feb 2026 13:14:18 GMT
Subject: Re: [PATCH 2/4] doc: finalize git-clone documentation conversion to synopsis style
Message-ID: <13939780.uLZWGnKmhe@piment-oiseau>
In-Reply-To: <6f7d027e-088a-4d66-92af-b8d1c32d730c@app.fastmail.com>

Thank you for taking time to scan through the changes.

I will reroll to fix all your comments.


On Sunday, 1 February 2026 13:04:13 CET Kristoffer Haugsbakk wrote:
> On Fri, Jan 23, 2026, at 22:15, Jean-Noël Avila via GitGitGadget wrote:

> 
> Doesn’t need to be done now in this series, but the “stuck form” of
> `--origin=<name>` is recommended by gitcli(7) for long optoins. This doc
> uses a mix of unstuck form (no `=`) and stuck form.
> 

Is this something that is automatically available, i.e can we already convert 
and advise so to writers in all pages?
For me, these synopsis series are a chance to push forward a larger range of 
reworks on formal formats such as this one.


> > +`--config <key>=<value>`::
> >  	Set a configuration variable in the newly-created repository;
> >  	this takes effect immediately after the repository is
> >  	initialized, but before the remote history is fetched or any
> 
> I was curious if you can use `--config=<key>=<value>` without tripping
> up the option parser. And you can:
> 
>     git clone --config=core.editor=something ...
> 

OK, will also rework.