public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Tom Schwindl <schwindl@posteo.de>,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Alejandro Colomar <alx@kernel.org>, linux-man@vger.kernel.org
Subject: Re: [PATCH] memcmp.3: wfix
Date: Wed, 15 Feb 2023 18:00:59 +0100	[thread overview]
Message-ID: <aaf147aa-fbf3-c649-f98f-6ea341fbb7dc@gmail.com> (raw)
In-Reply-To: <CQJ9NXF0GW79.O9TXGIQJ1PRK@morphine>


[-- Attachment #1.1: Type: text/plain, Size: 1324 bytes --]

Hi Tom,

On 2/15/23 17:11, Tom Schwindl wrote:
> On Wed Feb 15, 2023 at 4:18 PM CET, G. Branden Robinson wrote:
>> At 2023-02-15T13:07:50+0000, Tom Schwindl wrote:
>>> -On Linux, it may be necessary to implement such a function oneself.
>>> +On Linux, it may be necessary to implement such a function yourself.
>>
>> The existing language is sound.  What is the motivation for the change?
>>
>> Regards,
>> Branden
> 
> From a formal perspective it's probably fine. But as a reader, I think it sounds
> wrong. Or at least strange. That may be because I'm not a native speaker, but
> neither is the majority of the manpage readers.
> I simply think that "yourself" sounds better in this context. That's also the
> reason for this patch. I've read the manpage and hesitated for a short moment
> which, for me, indicates a poor choice of words. A `grep -i -r oneself` also
> only yields a single result, this manpage.

To me, the existing text reads fine.  Maybe it's because in my language
(Spanish), there's a similar expression for oneself, which may not exist
in other languages?

I'd keep it as it, unless I see more similar reports.  Anyway, thanks
for the report!

Cheers,

Alex
> 

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-02-15 17:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15 13:07 [PATCH] memcmp.3: wfix Tom Schwindl
2023-02-15 15:18 ` G. Branden Robinson
2023-02-15 16:11   ` Tom Schwindl
2023-02-15 17:00     ` Alejandro Colomar [this message]
2023-02-15 17:17 ` Jakub Wilk
2023-02-15 17:26   ` Alejandro Colomar
  -- strict thread matches above, loose matches on Subject: below --
2023-02-15 17:33 Tom Schwindl
2023-02-15 17:41 ` 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=aaf147aa-fbf3-c649-f98f-6ea341fbb7dc@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=alx@kernel.org \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=schwindl@posteo.de \
    /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