From: Alejandro Colomar <alx.manpages@gmail.com>
To: "Štěpán Němec" <stepnem@smrk.net>
Cc: linux-man@vger.kernel.org, Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH v1 0/2] Fix typos
Date: Sat, 8 Oct 2022 22:45:20 +0200 [thread overview]
Message-ID: <8706e023-c11e-fa2d-2d14-ab8a8dd0c434@gmail.com> (raw)
In-Reply-To: <20221008140514.501942-1-stepnem@smrk.net>
[-- Attachment #1.1: Type: text/plain, Size: 1788 bytes --]
On 10/8/22 16:05, Štěpán Němec wrote:
> On Sat, 08 Oct 2022 02:17:56 +0200
> Alejandro Colomar wrote:
>
>>> --- a/man2/pivot_root.2
>>> +++ b/man2/pivot_root.2
>>> @@ -60,7 +60,7 @@ must not be on the same mount as the current root.
>>> .IP \-
>>> \fIput_old\fP must be at or underneath \fInew_root\fP;
>>> that is, adding some nonnegative
>>> -number of "\fI/..\fP" prefixes to the pathname pointed to by
>>> +number of "\fI/..\fP" suffixes to the pathname pointed to by
>>
>> I'd like this change to be separate from the rest, as it's not an
>> obvious writing typo, but rather one that needs understanding the context.
>>
>> Would you mind splitting into a separate patch?
>
> Here it is. (I wanted to test the waters of submitting accumulated
> trivial fixes as a single patch, as I think it saves both some electrons
> and the resources of everyone else involved.)
Except that I don't agree on that one being that trivial :)
But yes, if you find many trivial typos, you can file them as a single
patch.
>
> I took this opportunity to squash in another missing article to the
> trivial typo patch (1/2).
>
That's fine.
Patch set applied.
Cheers,
Alex
> Thanks,
>
> Štěpán
>
> Štěpán Němec (2):
> memfd_create.2, mlock.2, poll.2, select.2, fopen.3, capabilities.7: tfix
> pivot_root.2: Fix a typo/thinko
>
> man2/memfd_create.2 | 2 +-
> man2/mlock.2 | 2 +-
> man2/pivot_root.2 | 2 +-
> man2/poll.2 | 2 +-
> man2/select.2 | 2 +-
> man3/fopen.3 | 2 +-
> man7/capabilities.7 | 4 ++--
> 7 files changed, 8 insertions(+), 8 deletions(-)
>
>
> base-commit: a4a073ae7737fb8f20c390a60b8555a7cfdace98
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-10-08 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 15:46 [PATCH] mlock.2, pivot_root.2, poll.2, select.2, fopen.3, capabilities.7: tfix Štěpán Němec
2022-10-08 0:17 ` Alejandro Colomar
2022-10-08 14:05 ` [PATCH v1 0/2] Fix typos Štěpán Němec
2022-10-08 14:05 ` [PATCH v1 1/2] memfd_create.2, mlock.2, poll.2, select.2, fopen.3, capabilities.7: tfix Štěpán Němec
2022-10-08 14:05 ` [PATCH v1 2/2] pivot_root.2: Fix a typo/thinko Štěpán Němec
2022-10-08 20:45 ` 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=8706e023-c11e-fa2d-2d14-ab8a8dd0c434@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=stepnem@smrk.net \
/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