public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
	Samanta Navarro <ferivoz@riseup.net>
Cc: linux-man@vger.kernel.org, mtk.manpages@gmail.com
Subject: Re: [patch] futex.2, mount_setattr.2, proc.5, netlink.7, tcp.7: tfix
Date: Mon, 22 Nov 2021 18:12:48 +0100	[thread overview]
Message-ID: <5f765ff0-59a2-7a54-873c-4632eed575d9@gmail.com> (raw)
In-Reply-To: <20211113124154.lazhqkb6qms7mpbo@localhost.localdomain>

Hi Branden and Samanta,

On 11/13/21 13:41, G. Branden Robinson wrote:
> Hi Samanta,
> 
> At 2021-11-13T11:58:08+0000, Samanta Navarro wrote:
>> Typos found with codespell.
> [...]
>> diff --git a/man2/mount_setattr.2 b/man2/mount_setattr.2
>> index 77233f5..ca56256 100644
>> --- a/man2/mount_setattr.2
>> +++ b/man2/mount_setattr.2
>> @@ -986,7 +986,7 @@ main(int argc, char *argv[])
>>   .\"     because. Because making assumptions about the current working directory
>>   .\"     of the calling process is just too easy to get wrong; especially when
>>   .\"     pivot_root() or chroot() are in play.
>> -.\"     My absolut preference (joke intended) is to open a well-known starting
>> +.\"     My absolute preference (joke intended) is to open a well-known starting
>>   .\"     point with an absolute path to get a dirfd and then scope all future
>>   .\"     operations beneath that dirfd. This already works with old-style
>>   .\"     openat() and _very_ cautious programming but openat2() and its
> 
> I always thought the foregoing was a double entendre expressing the
> author's taste for vodka...

Yes.  There have been other attempts to patch this[1], but I'll defend 
the author's joke, even if I don't share his preferences for liquid 
ingestion. :)

[1]: 
https://lore.kernel.org/linux-man/20210910200429.4816-3-jwilk@jwilk.net/

Cheers,
Alex
-- 
Alejandro Colomar
Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2021-11-22 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-13 11:58 [patch] futex.2, mount_setattr.2, proc.5, netlink.7, tcp.7: tfix Samanta Navarro
2021-11-13 12:41 ` G. Branden Robinson
2021-11-22 17:12   ` Alejandro Colomar (man-pages) [this message]
2021-11-22 17:14     ` Alejandro Colomar (man-pages)
2021-11-24 11:59       ` Samanta Navarro
2021-11-29 12:17         ` Alejandro Colomar (man-pages)

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=5f765ff0-59a2-7a54-873c-4632eed575d9@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=ferivoz@riseup.net \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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