From: Alejandro Colomar <alx@kernel.org>
To: Lennart Jablonka <humm@ljabl.com>
Cc: linux-man@vger.kernel.org,
"G. Branden Robinson" <g.branden.robinson@gmail.com>
Subject: Re: [PATCH] string_copying.7: tfix
Date: Sat, 29 Jul 2023 13:09:01 +0200 [thread overview]
Message-ID: <c805f5d7-6db9-2a94-26f6-e5e4e12bb7b5@kernel.org> (raw)
In-Reply-To: <ZMROl_ZM80HoB9Ss@fluorine.ljabl.com>
[-- Attachment #1.1: Type: text/plain, Size: 1507 bytes --]
On 2023-07-29 01:26, Lennart Jablonka wrote:
[...]
>>> @@ -444,8 +444,8 @@ is a more useful alternative to this function.
>>> .\" ----- DESCRIPTION :: Functions :: zustr2ustp(3) --------------------/
>>> .TP
>>> .BR zustr2ustp (3)
>>> -This function copies the input character sequence
>>> -contained in a null-padded wixed-width buffer,
>>> +This function copies the input character sequence,
>>
>> I believe the below is like a parenthetical, which is why I put it
>> between commas; isn't it? Although your version also looks good.
>>
>>> +contained in a null-padded fixed-width buffer,
>>
>> Ok
>>
>>> into a destination character sequence.
>
> The “contained in a null-padded fixed-width buffer” indeed looks
> like a parenthetical (or rather, a non-restrictive participial
> clause—the “contained” is the participle), which is why it should
> be between commas. You didn’t do quite that: You put a comma
> after it, but not before.
>
> This case is what I tried to explain: You set off the “into
> a destination character sequence” prepositional phrase (the “into”
> being the preposition) by a comma. You did not surround the
> participial clause by commas. That’s what I did.
D'oh! I misread the diff; I thought you were removing the comma
instead of adding it. I certainly like your addition.
Cheers,
Alex
--
<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-07-29 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 18:41 [PATCH] string_copying.7: tfix Lennart Jablonka
2023-07-28 21:31 ` Alejandro Colomar
2023-07-28 23:26 ` Lennart Jablonka
2023-07-29 11:09 ` Alejandro Colomar [this message]
2023-07-29 9:50 ` G. Branden Robinson
2023-07-29 11:17 ` Alejandro Colomar
2023-07-29 11:29 ` 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=c805f5d7-6db9-2a94-26f6-e5e4e12bb7b5@kernel.org \
--to=alx@kernel.org \
--cc=g.branden.robinson@gmail.com \
--cc=humm@ljabl.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