git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jean-Noël AVILA" <avila.jn@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH] doc/gitremote-helpers: fix more missing single-quotes
Date: Sat, 23 Mar 2024 20:58:39 +0100	[thread overview]
Message-ID: <22254967.EfDdHjke4D@cayenne> (raw)
In-Reply-To: <xmqq7chvblgr.fsf@gitster.g>

Le jeudi 21 mars 2024, 17:25:56 CET Junio C Hamano a écrit :
> Jean-Noël Avila <avila.jn@gmail.com> writes:
> 
> >> -'option deepen-relative {'true'|'false'}::
> >> +'option deepen-relative' {'true'|'false'}::
> >>  	Deepens the history of a shallow repository relative to
> >>  	current boundary. Only valid when used with "option depth".
> >
> > The syntax for describing alternatives is specified as (true|false).
> 
> Hmmmm, here, true and false are to be given verbatim.

In such case, it's (`true`|`false`) . As well as the command before.

> 
> > Also, in my reworks of syntax, I chose to remove all formatting from the
> > term parts of the description lists.
> 
> I know we added the _<placeholder>_ thing, but have we added these
> to Documentation/CodingGuidelines yet?
> 
> Thanks.
> 
> 

No, we haven't. 

I skimmed over different documentation projects and there's no real consensus 
on what the formatting should be in detail, except for some common rules.
man-pages(7) gives some good hints that we should adhere to, which are echoed 
in the guide of asciidoc: https://docs.asciidoctor.org/asciidoctor/latest/
manpage-backend/ . Basically, verbatim are in bold, and variables are in 
italic.

In our man pages, the asciidoc verbatim are rendered as bold and asciidoc 
emphasis are rendered as underlined, just like italics,  which adheres to the 
principles,

Note that bold/verbatim are usually also used in terms of description lists.

I'm totally ok to change the CodingGuidelines and reroll git-clone and git-
init with these new rules.



  reply	other threads:[~2024-03-23 19:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20  9:17 [PATCH] doc/gitremote-helpers: fix more missing single-quotes Jeff King
2024-03-20 16:59 ` Junio C Hamano
2024-03-21 10:28 ` Jean-Noël Avila
2024-03-21 16:25   ` Junio C Hamano
2024-03-23 19:58     ` Jean-Noël AVILA [this message]
2024-03-24  2:19       ` Junio C Hamano
2024-03-24 15:41         ` Jean-Noël AVILA
2024-03-24 16:15           ` Junio C Hamano
2024-03-22  6:39   ` Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=22254967.EfDdHjke4D@cayenne \
    --to=avila.jn@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).