public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Štěpán Němec" <stepnem@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>, linux-man@vger.kernel.org
Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Subject: Re: [PATCH 1/6] getrlimit.2: tfix
Date: Mon, 01 Aug 2022 16:09:01 +0200	[thread overview]
Message-ID: <20220801160901+0200.350977-stepnem@gmail.com> (raw)
In-Reply-To: <d1e19ee4-d75a-86a5-e6c1-32dfd7460a3c@gmail.com>

On Mon, 01 Aug 2022 15:03:29 +0200
Alejandro Colomar wrote:

> On 7/29/22 13:45, Štěpán Němec wrote:
>> Signed-off-by: Štěpán Němec <stepnem@gmail.com>
>
> I applied the 6 patches from the patch set, including the controversial 
> \~ vs '\ ' one.  I think that fix is better as a separate one, which 
> should include references to the SI that I quoted.

Thank you. For convenience, here is the one '\~' outlier (I was sitting
on that one in case Branden or anyone else would still want to chime in:
the conflict with groff_man(7) does seem unfortunate), feel free to do
with it as you please:

-- >8 --
From: =?UTF-8?q?=C5=A0t=C4=9Bp=C3=A1n=20N=C4=9Bmec?= <stepnem@gmail.com>
Date: Sat, 30 Jul 2022 20:42:03 +0200
Subject: [PATCH] ioctl_fideduperange.2: use '\ ' instead of '\~' between
 number and unit

Signed-off-by: Štěpán Němec <stepnem@gmail.com>
---
 man2/ioctl_fideduperange.2 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man2/ioctl_fideduperange.2 b/man2/ioctl_fideduperange.2
index 8bf114e8bb3b..585ed8beb9d7 100644
--- a/man2/ioctl_fideduperange.2
+++ b/man2/ioctl_fideduperange.2
@@ -100,7 +100,7 @@ and the struct
 array must not exceed the system page size.
 The maximum size of
 .I src_length
-is filesystem dependent and is typically 16\~MiB.
+is filesystem dependent and is typically 16\ MiB.
 This limit will be enforced silently by the filesystem.
 By convention, the storage used by
 .I src_fd

-- 8< --

> I'll try to apply a global fix about spacing.  Anyway, could you please 
> share the grep commands you used to find it?  It might help me see you 
> command, in case I miss some corner cases.

Oh, nothing fancy at all, just grepping for '\ ' or '\~', e.g.

  grep -R '\\~' man*

-- 
Štěpán

      reply	other threads:[~2022-08-01 14:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29 11:45 [PATCH 1/6] getrlimit.2: tfix Štěpán Němec
2022-08-01 13:03 ` Alejandro Colomar
2022-08-01 14:09   ` Štěpán Němec [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=20220801160901+0200.350977-stepnem@gmail.com \
    --to=stepnem@gmail.com \
    --cc=alx.manpages@gmail.com \
    --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