public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Svetly Todorov <svetly.todorov@memverge.com>
Cc: linux-man@vger.kernel.org, gregory.price@memverge.com,
	ying.huang@intel.com
Subject: Re: [PATCH v2] man2: add MPOL_WEIGHTED_INTERLEAVE documentation
Date: Fri, 15 Mar 2024 20:22:52 +0100	[thread overview]
Message-ID: <ZfSgDOLBqw1Kyz8X@debian> (raw)
In-Reply-To: <ZfSf3f7baqC1N_ha@debian>

[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]

On Fri, Mar 15, 2024 at 08:22:05PM +0100, Alejandro Colomar wrote:
> 
> Path names should go in italics.  See groff_man(7):

Oops, that's groff_man_style(7), actually.

>      .I [text]
>             Set  text in an italic or oblique face.  If no argument is
>             given, a one‐line input trap is planted; text on the  next
>             line,  which can be further formatted with a macro, is set
>             in an italic or oblique face.
> 
>             Use italics for file and path names, [...]
>                     An exception involves variant text  in  a  context
>             already  typeset  in  italics,  such as file or path names
>             with replaceable components; in  such  cases,  follow  the
>             convention  of  mathematical  typography:  set the file or
>             path name in italics as usual but use roman for the  vari‐
>             ant  part  (see  .IR  and .RI below), and italics again in
>             running roman text when referring to the variant material.

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-03-15 19:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15 18:02 [PATCH v2] man2: add MPOL_WEIGHTED_INTERLEAVE documentation Svetly Todorov
2024-03-15 19:22 ` Alejandro Colomar
2024-03-15 19:22   ` Alejandro Colomar [this message]
2024-03-15 23:00     ` Svetly Todorov
2024-03-15 23:21       ` Alejandro Colomar
2024-03-18  2:00 ` Huang, Ying
2024-03-18 16:34   ` Svetly Todorov

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=ZfSgDOLBqw1Kyz8X@debian \
    --to=alx@kernel.org \
    --cc=gregory.price@memverge.com \
    --cc=linux-man@vger.kernel.org \
    --cc=svetly.todorov@memverge.com \
    --cc=ying.huang@intel.com \
    /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