From: John Hubbard <jhubbard@nvidia.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
<linux-man@vger.kernel.org>, <linux-mm@kvack.org>,
Vahid Noormofidi <vnoormof@nvidia.com>,
Matthew Wilcox <willy@infradead.org>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Carsten Grohmann <carstengrohmann@gmx.de>,
Mike Frysinger <vapier@gentoo.org>
Subject: Re: [PATCH] man5/tmpfs.5: fix typo in reference to CONFIG_TRANSPARENT_HUGEPAGE
Date: Fri, 28 Jul 2023 12:18:56 -0700 [thread overview]
Message-ID: <88509788-e614-06a4-5a89-0d060bc7defc@nvidia.com> (raw)
In-Reply-To: <dff13ab7-bd33-ce26-792f-956b57924df6@kernel.org>
On 7/28/23 12:04, Alejandro Colomar wrote:
...
> I've slightly reworded the commit message:
>
> - Use tmpfs.5: instead of man5/tmpfs.5:. We only specify the last
> filename in the path (see the git log).
>
> - It really wasn't a typo, because the previous text was written in
> a time when that was the correct spelling. So, instead, I've
> changed it to talk about an update, rather than a typo fix.
>
Oh yes, thanks for fixing that up! That's perfect.
I wrote the subject line early on, when I initially thought it was a
typo. After looking more closely it became clear what happened, but I
failed to update the subject line accordingly, so I really appreciate
that you caught it.
thanks,
--
John Hubbard
NVIDIA
prev parent reply other threads:[~2023-07-28 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 2:05 John Hubbard
2023-07-19 19:59 ` Alejandro Colomar
2023-07-19 20:13 ` John Hubbard
2023-07-20 8:03 ` Alejandro Colomar
2023-07-28 19:04 ` Alejandro Colomar
2023-07-28 19:18 ` John Hubbard [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=88509788-e614-06a4-5a89-0d060bc7defc@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=alx@kernel.org \
--cc=carstengrohmann@gmx.de \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtk.manpages@gmail.com \
--cc=vapier@gentoo.org \
--cc=vnoormof@nvidia.com \
--cc=willy@infradead.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