From: Alejandro Colomar <alx.manpages@gmail.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v3 5/9] adjtimex.2, clone.2, mprotect.2, open.2, syscall.2, regex.3: ffix, wfix
Date: Thu, 20 Apr 2023 14:52:19 +0200 [thread overview]
Message-ID: <d1d90b61-9d3e-e124-c0fb-19d426540416@gmail.com> (raw)
In-Reply-To: <45hc4nxirbxf5oe23noyfpg4w24vtwfpnye5y5sgozy5j3i22a@5hueh33r4bos>
[-- Attachment #1.1: Type: text/plain, Size: 3739 bytes --]
On 4/20/23 14:12, наб wrote:
> Use "bitwise OR" instead of "bitwise-or" (with fonts).
> No other pages spell it like this.
>
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Patch applied. Thanks.
> ---
> Range-diff against v2:
> 1: 1ccffe37b < -: --------- regex.3: ffix
> -: --------- > 1: 830173bb5 adjtimex.2, clone.2, mprotect.2, open.2, syscall.2, regex.3: ffix, wfix
I rewrote the subject to:
man*/: ffix, wfix
>
> idk if this did anything
Heh, it didn't do much. What happened is that the patches are so
different, that git thinks you just removed one patch, and wrote
a different one from scratch. Anyway, I find it useful most of
the time.
Cheers,
Alex
>
> man2/adjtimex.2 | 2 +-
> man2/clone.2 | 2 +-
> man2/mprotect.2 | 2 +-
> man2/open.2 | 2 +-
> man2/syscall.2 | 2 +-
> man3/regex.3 | 4 ++--
> 6 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/man2/adjtimex.2 b/man2/adjtimex.2
> index 523347de2..40b05cb0e 100644
> --- a/man2/adjtimex.2
> +++ b/man2/adjtimex.2
> @@ -90,7 +90,7 @@ the constants used for
> .BR ntp_adjtime ()
> are equivalent but differently named.)
> It is a bit mask containing a
> -.RI bitwise- or
> +bitwise OR
> combination of zero or more of the following bits:
> .TP
> .B ADJ_OFFSET
> diff --git a/man2/clone.2 b/man2/clone.2
> index 42ee3fee8..ec43841eb 100644
> --- a/man2/clone.2
> +++ b/man2/clone.2
> @@ -413,7 +413,7 @@ mask in the remainder of this page.
> .PP
> The
> .I flags
> -mask is specified as a bitwise-OR of zero or more of
> +mask is specified as a bitwise OR of zero or more of
> the constants listed below.
> Except as noted below, these flags are available
> (and have the same effect) in both
> diff --git a/man2/mprotect.2 b/man2/mprotect.2
> index 52c14da05..5a829dafe 100644
> --- a/man2/mprotect.2
> +++ b/man2/mprotect.2
> @@ -43,7 +43,7 @@ signal for the process.
> .I prot
> is a combination of the following access flags:
> .B PROT_NONE
> -or a bitwise-or of the other values in the following list:
> +or a bitwise OR of the other values in the following list:
> .TP
> .B PROT_NONE
> The memory cannot be accessed at all.
> diff --git a/man2/open.2 b/man2/open.2
> index 77c06b55d..b5aff887c 100644
> --- a/man2/open.2
> +++ b/man2/open.2
> @@ -123,7 +123,7 @@ respectively.
> .PP
> In addition, zero or more file creation flags and file status flags
> can be
> -.RI bitwise- or 'd
> +bitwise ORed
> in
> .IR flags .
> The
> diff --git a/man2/syscall.2 b/man2/syscall.2
> index 3eba62182..55233ac51 100644
> --- a/man2/syscall.2
> +++ b/man2/syscall.2
> @@ -235,7 +235,7 @@ nuances:
> In order to indicate that a system call is called under the x32 ABI,
> an additional bit,
> .BR __X32_SYSCALL_BIT ,
> -is bitwise-ORed with the system call number.
> +is bitwise ORed with the system call number.
> The ABI used by a process affects some process behaviors,
> including signal handling or system call restarting.
> .IP \[bu]
> diff --git a/man3/regex.3 b/man3/regex.3
> index 3b504a4d5..3ee58f61d 100644
> --- a/man3/regex.3
> +++ b/man3/regex.3
> @@ -56,7 +56,7 @@ pattern buffer.
> .PP
> .I cflags
> is the
> -.RB bitwise- or
> +bitwise OR
> of zero or more of the following:
> .TP
> .B REG_EXTENDED
> @@ -121,7 +121,7 @@ and
> are used to provide information regarding the location of any matches.
> .I eflags
> is the
> -.RB bitwise- or
> +bitwise OR
> of zero or more of the following flags:
> .TP
> .B REG_NOTBOL
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-04-20 12:52 UTC|newest]
Thread overview: 143+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 17:47 [PATCH 1/2] regex.3: note that pmatch is still used if REG_NOSUB if REG_STARTEND наб
2023-04-19 17:48 ` [PATCH 2/2] regex.3: improve REG_STARTEND наб
2023-04-19 20:23 ` Alejandro Colomar
2023-04-19 21:20 ` наб
2023-04-19 21:45 ` Alejandro Colomar
2023-04-19 23:23 ` [PATCH v2 1/9] regex.3: note that pmatch is still used if REG_NOSUB if REG_STARTEND наб
2023-04-20 11:21 ` Alejandro Colomar
2023-04-19 23:23 ` [PATCH v2 2/9] regex.3: improve REG_STARTEND наб
2023-04-20 10:00 ` G. Branden Robinson
2023-04-20 11:13 ` наб
2023-04-20 18:33 ` G. Branden Robinson
2023-04-20 22:29 ` Alejandro Colomar
2023-04-21 5:00 ` G. Branden Robinson
2023-04-21 8:06 ` a straw-man `SR` man(7) macro for (sub)section cross references (was: [PATCH v2 2/9] regex.3: improve REG_STARTEND) G. Branden Robinson
2023-04-21 11:07 ` [PATCH v2 2/9] regex.3: improve REG_STARTEND Alejandro Colomar
2023-06-02 0:12 ` Alejandro Colomar
2023-06-02 0:49 ` наб
2023-06-03 17:30 ` Alejandro Colomar
2023-04-19 23:23 ` [PATCH v2 3/9] regex.3: ffix наб
2023-04-20 11:23 ` Alejandro Colomar
2023-04-19 23:23 ` [PATCH v2 4/9] regex.3: wfix наб
2023-04-20 11:27 ` Alejandro Colomar
2023-04-19 23:23 ` [PATCH v2 5/9] regex.3: ffix наб
2023-04-20 11:28 ` Alejandro Colomar
2023-04-20 12:12 ` [PATCH v3 5/9] adjtimex.2, clone.2, mprotect.2, open.2, syscall.2, regex.3: ffix, wfix наб
2023-04-20 12:52 ` Alejandro Colomar [this message]
2023-04-20 13:03 ` Alejandro Colomar
2023-04-20 14:13 ` наб
2023-04-20 14:19 ` Alejandro Colomar
2023-04-20 18:42 ` G. Branden Robinson
2023-04-20 22:40 ` Alejandro Colomar
2023-04-19 23:25 ` [PATCH v2 6/9] regex.3, regex_t.3type, regmatch_t.3type, regoff_t.3type: move in with regex.3 наб
2023-04-20 11:31 ` Alejandro Colomar
2023-04-20 13:02 ` [PATCH v4 1/6] regex.3: Fix subsection headings наб
2023-04-20 13:13 ` Alejandro Colomar
2023-04-20 13:24 ` наб
2023-04-20 13:35 ` Alejandro Colomar
2023-04-20 15:35 ` [PATCH v5 0/8] regex.3 momento наб
2023-04-20 15:35 ` [PATCH v5 1/8] regex.3: Desoupify regcomp() description наб
2023-04-20 16:37 ` Alejandro Colomar
2023-04-20 15:35 ` [PATCH v5 2/8] regex.3: Desoupify regexec() description наб
2023-04-20 15:35 ` [PATCH v5 3/8] regex.3: Desoupify regerror() description наб
2023-04-20 16:42 ` Alejandro Colomar
2023-04-20 18:50 ` наб
2023-04-20 16:50 ` Alejandro Colomar
2023-04-20 17:23 ` Alejandro Colomar
2023-04-20 18:46 ` наб
2023-04-20 22:45 ` Alejandro Colomar
2023-04-20 23:05 ` наб
2023-04-20 15:35 ` [PATCH v5 4/8] regex.3: Improve REG_STARTEND наб
2023-04-20 17:29 ` Alejandro Colomar
2023-04-20 19:30 ` наб
2023-04-20 19:33 ` наб
2023-04-20 23:01 ` Alejandro Colomar
2023-04-21 0:13 ` наб
2023-04-20 15:36 ` [PATCH v5 5/8] regex.3, regex_t.3type, regmatch_t.3type, regoff_t.3type: Move & link regex_t.3type into regex.3 наб
2023-04-20 15:36 ` [PATCH v5 6/8] regex.3: Finalise move of reg*.3type наб
2023-04-20 15:36 ` [PATCH v5 7/8] regex.3: Destandardeseify Match offsets наб
2023-04-20 15:36 ` [PATCH v5 8/8] regex.3: Further clarify the sole purpose of REG_NOSUB наб
2023-04-20 19:36 ` [PATCH v6 0/8] regex.3 momento наб
2023-04-20 19:36 ` [PATCH v6 1/8] regex.3: Desoupify regexec() description наб
2023-04-20 23:24 ` Alejandro Colomar
2023-04-21 0:33 ` наб
2023-04-21 0:49 ` Alejandro Colomar
2023-04-20 19:36 ` [PATCH v6 2/8] regex.3: Desoupify regerror() description наб
2023-04-20 19:37 ` [PATCH v6 3/8] regex.3: Desoupify regfree() description наб
2023-04-20 23:35 ` Alejandro Colomar
2023-04-21 0:27 ` наб
2023-04-21 0:37 ` [PATCH v7 " наб
2023-04-21 0:58 ` [PATCH v6 " Alejandro Colomar
2023-04-21 1:24 ` [PATCH v7a " наб
2023-04-21 1:55 ` Alejandro Colomar
2023-04-20 19:37 ` [PATCH v6 4/8] regex.3: Improve REG_STARTEND наб
2023-04-20 23:15 ` Alejandro Colomar
2023-04-21 0:39 ` [PATCH v7 " наб
2023-04-21 1:42 ` Alejandro Colomar
2023-04-21 2:16 ` наб
2023-04-21 9:45 ` Alejandro Colomar
2023-04-21 12:13 ` наб
2023-04-21 12:21 ` Alejandro Colomar
2023-04-21 12:23 ` Alejandro Colomar
2023-04-21 10:19 ` Jakub Wilk
2023-04-21 10:22 ` Alejandro Colomar
2023-04-21 10:44 ` Jakub Wilk
2023-04-21 11:16 ` Alejandro Colomar
2023-04-21 11:34 ` наб
2023-04-21 12:46 ` Jakub Wilk
2023-04-20 19:37 ` [PATCH v6 5/8] regex.3, regex_t.3type, regmatch_t.3type, regoff_t.3type: Move & link regex_t.3type into regex.3 наб
2023-04-20 19:37 ` [PATCH v6 6/8] regex.3: Finalise move of reg*.3type наб
2023-04-20 19:37 ` [PATCH v6 7/8] regex.3: Destandardeseify Match offsets наб
2023-04-20 19:37 ` [PATCH v6 8/8] regex.3: Further clarify the sole purpose of REG_NOSUB наб
2023-04-21 2:01 ` [PATCH v6 0/8] regex.3 momento Alejandro Colomar
2023-04-21 2:48 ` [PATCH v8 0/5] " наб
2023-04-21 2:48 ` [PATCH v8 1/5] regex.3: Desoupify regerror() description наб
2023-04-21 10:06 ` Alejandro Colomar
2023-04-21 12:03 ` [PATCH v9] " наб
2023-04-21 12:26 ` Alejandro Colomar
2023-04-21 12:27 ` Alejandro Colomar
2023-04-21 2:48 ` [PATCH v8 2/5] regex.3, regex_t.3type, regmatch_t.3type, regoff_t.3type: Move & link regex_t.3type into regex.3 наб
2023-04-21 11:55 ` Alejandro Colomar
2023-04-21 11:57 ` Alejandro Colomar
2023-04-21 11:57 ` Alejandro Colomar
2023-04-21 2:48 ` [PATCH v8 3/5] regex.3: Finalise move of reg*.3type наб
2023-04-21 10:33 ` Alejandro Colomar
2023-04-21 10:34 ` Alejandro Colomar
2023-04-21 11:26 ` наб
2023-04-21 11:36 ` Alejandro Colomar
2023-04-21 11:49 ` наб
[not found] ` <1d2d0aa8-cb28-2d7f-c48b-7a02f907cb5b@gmail.com>
2023-04-21 11:57 ` Ralph Corderoy
2023-04-21 11:59 ` Alejandro Colomar
2023-04-21 12:03 ` Alejandro Colomar
2023-04-21 12:09 ` Ralph Corderoy
2023-04-21 12:14 ` Alejandro Colomar
2023-04-21 2:49 ` [PATCH v8 4/5] regex.3: Destandardeseify Match offsets наб
2023-04-21 10:36 ` Alejandro Colomar
2023-04-21 12:55 ` [PATCH v9] " наб
2023-04-21 13:15 ` Alejandro Colomar
2023-04-21 13:29 ` [PATCH v9a] " наб
2023-04-21 13:55 ` Alejandro Colomar
2023-04-21 2:49 ` [PATCH v8 5/5] regex.3: Further clarify the sole purpose of REG_NOSUB наб
2023-04-21 11:44 ` Alejandro Colomar
2023-04-21 10:00 ` [PATCH v8 0/5] regex.3 momento Alejandro Colomar
2023-04-20 13:02 ` [PATCH v4 2/6] regex.3: Desoupify function descriptions наб
2023-04-20 14:00 ` Alejandro Colomar
2023-04-20 14:37 ` наб
2023-04-20 13:02 ` [PATCH v4 3/6] regex.3: Improve REG_STARTEND наб
2023-04-20 14:04 ` Alejandro Colomar
2023-04-20 13:02 ` [PATCH v4 4/6] regex.3, regex_t.3type: Move regex_t.3type into regex.3 наб
2023-04-20 13:02 ` [PATCH v4 5/6] regex.3, regex_t.3type, regmatch_t.3type, regoff_t.3type: Move in with regex.3 наб
2023-04-20 14:07 ` Alejandro Colomar
2023-04-20 13:02 ` [PATCH v4 6/6] regex.3: Destandardeseify Match offsets наб
2023-04-20 14:10 ` Alejandro Colomar
2023-04-20 15:05 ` наб
2023-04-20 18:51 ` G. Branden Robinson
2023-04-21 11:34 ` Alejandro Colomar
2023-04-19 23:25 ` [PATCH v2 7/9] regex.3: destandardeseify Byte offsets наб
2023-04-19 23:26 ` [PATCH v2 8/9] regex.3: desoupify function descriptions наб
2023-04-20 11:15 ` [PATCH v3 " наб
2023-04-20 11:43 ` Alejandro Colomar
2023-04-20 11:50 ` наб
2023-04-19 23:26 ` [PATCH v2 9/9] regex.3: fix subsection headings наб
2023-04-20 11:17 ` [PATCH v3 " наб
2023-04-19 19:51 ` [PATCH 1/2] regex.3: note that pmatch is still used if REG_NOSUB if REG_STARTEND Alejandro Colomar
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=d1d90b61-9d3e-e124-c0fb-19d426540416@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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 NNTP newsgroup(s).