All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 3/4] man2/open.2: ffix
Date: Tue, 16 Jan 2024 16:18:26 +0100	[thread overview]
Message-ID: <ZaaeQubgNxAQYCvH@debian> (raw)
In-Reply-To: <20240116134009.3hufaahoy3kk4os6@illithid>

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

On Tue, Jan 16, 2024 at 07:40:09AM -0600, G. Branden Robinson wrote:
> Migrate man page cross reference in non-filled context to font
> alternation macro.  This is to prepare it for `MR` migration.
> 
> Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com>
> ---
>  man2/open.2 | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/man2/open.2 b/man2/open.2
> index f37ddbed0..42716ed8e 100644
> --- a/man2/open.2
> +++ b/man2/open.2
> @@ -46,7 +46,9 @@ .SH SYNOPSIS
>  .BI "int openat(int " dirfd ", const char *" pathname ", int " flags ", ..."
>  .BI "           \fR/*\fP mode_t " mode " \fR*/\fP );"
>  .P
> -/* Documented separately, in \fBopenat2\fP(2): */
> +/* Documented separately, in \c
> +.BR openat2 :\c

Did you forget the (2)?

> +\& */
>  .BI "int openat2(int " dirfd ", const char *" pathname ,
>  .BI "           const struct open_how *" how ", size_t " size );
>  .fi
> -- 
> 2.30.2
> 



-- 
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.

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

  reply	other threads:[~2024-01-16 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 13:40 [PATCH 3/4] man2/open.2: ffix G. Branden Robinson
2024-01-16 15:18 ` Alejandro Colomar [this message]
2024-01-16 15:34   ` G. Branden Robinson

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=ZaaeQubgNxAQYCvH@debian \
    --to=alx@kernel.org \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.