All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Mark Wielaard <mark@klomp.org>
Cc: linux-man@vger.kernel.org, "Alexandra Hájková" <ahajkova@redhat.com>
Subject: Re: [PATCH v3] close_range.2: Add _GNU_SOURCE and unistd.h to SYNOPSIS
Date: Sun, 18 Feb 2024 14:15:59 +0100	[thread overview]
Message-ID: <ZdIDDw_4Vd2lviE7@debian> (raw)
In-Reply-To: <20240218120035.GE16832@gnu.wildebeest.org>

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

Hi Mark,

On Sun, Feb 18, 2024 at 01:00:35PM +0100, Mark Wielaard wrote:
> Note that there is now one line which is > 80 chars.
> You can fix that using this from the original fix,
> that splits and indents the comment on two lines:
> 
> > > +.BR "#include <linux/close_range.h>" " /* Definition of " CLOSE_RANGE_* "
> > > +.BR "" "                                  constants */"

I've amended it with your original code, and also realized that we can
put the function prototype in a single line now:

<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=2fe73d74a661e7a9122482b840150e6ef867cdd6>

diff --git a/man2/close_range.2 b/man2/close_range.2
index bd5d10233..b0c9ef66e 100644
--- a/man2/close_range.2
+++ b/man2/close_range.2
@@ -14,11 +14,11 @@ .SH SYNOPSIS
 .BR "#define _GNU_SOURCE" "         /* See feature_test_macros(7) */"
 .B #include <unistd.h>
 .P
-.BR "#include <linux/close_range.h>" " /* Definition of " CLOSE_RANGE_* \
-" constants */"
+.BR "#include <linux/close_range.h>" " /* Definition of " CLOSE_RANGE_* "
+.BR "" "                                  constants */"
 .P
-.BI "int close_range(unsigned int " first ", unsigned int " last ,
-.BI "                int " flags );
+.BI "int close_range(unsigned int " first ", unsigned int " last \
+", int " flags );
 .fi
 .SH DESCRIPTION
 The


Have a lovely day!
Alex

-- 
<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 --]

      parent reply	other threads:[~2024-02-18 13:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12 12:07 [PATCH v3] close_range.2: Add _GNU_SOURCE and unistd.h to SYNOPSIS Mark Wielaard
2024-02-18  1:09 ` Alejandro Colomar
2024-02-18 12:00   ` Mark Wielaard
2024-02-18 13:08     ` Alejandro Colomar
2024-02-18 14:14       ` man page base paragraph inset/indentation (was: [PATCH v3] close_range.2: Add _GNU_SOURCE and unistd.h to SYNOPSIS) G. Branden Robinson
2024-02-18 15:18         ` Alejandro Colomar
2024-02-18 16:36           ` groff 1.24 scheduling thoughts (was: man page base paragraph inset/indentation) G. Branden Robinson
2024-02-18 13:15     ` 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=ZdIDDw_4Vd2lviE7@debian \
    --to=alx@kernel.org \
    --cc=ahajkova@redhat.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mark@klomp.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.