Linux-man Archive on 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 v2] man2/open.2: ffix
Date: Tue, 16 Jan 2024 16:49:11 +0100	[thread overview]
Message-ID: <Zaald3N1JU7HzJDT@debian> (raw)
In-Reply-To: <20240116153355.g5rspmbm3dqty5f4@illithid>

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

On Tue, Jan 16, 2024 at 09:33:55AM -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>
> ---
> v2: Fix thinko omitting "(2)".
> 
>  man2/open.2 | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/man2/open.2 b/man2/open.2
> index f37ddbed0..8c791fa47 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 (2):\c
> +\& */

Patch applied /:)

Cheers,
Alex

>  .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:49 UTC|newest]

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

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=Zaald3N1JU7HzJDT@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).