From: Alejandro Colomar <alx.manpages@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>, linux-man@vger.kernel.org
Cc: NeilBrown <neilb@suse.de>, Jeff Layton <jlayton@kernel.org>,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH] utime.2, utimensat.2: explicitly mention ctime changing.
Date: Thu, 25 Aug 2022 13:19:34 +0200 [thread overview]
Message-ID: <5198926c-b0af-8fba-bfcb-8d222f5990e1@gmail.com> (raw)
In-Reply-To: <20220825083736.pnwuytunzhvq4hwx@jwilk.net>
[-- Attachment #1.1: Type: text/plain, Size: 729 bytes --]
Hi Jakub, Neil,
On 8/25/22 10:37, Jakub Wilk wrote:
> * NeilBrown <neilb@suse.de>, 2022-08-25 10:20:
>> I will in future, but you might like to update
>> https://www.kernel.org/doc/man-pages/patches.html to make it clear
>> that "either" isn't really wanted and "both" maintainers should get
>> the patch.
>
> Also: can we have this information directly in the CONTRIBUTING file?
>
Yup, CONTRIBUTING updated:
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=974845c5c3a6d26318ac5d0ab6aaf493d5c43979>
However, I don't know what's the process to update the website, so it'll
take some time to update.
Cheers,
Alex
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-08-25 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 1:21 [PATCH] utime.2, utimensat.2: explicitly mention ctime changing NeilBrown
2022-08-24 10:15 ` Jeff Layton
2022-08-24 11:49 ` Alejandro Colomar
2022-08-25 0:20 ` NeilBrown
2022-08-25 8:37 ` Jakub Wilk
2022-08-25 11:19 ` Alejandro Colomar [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=5198926c-b0af-8fba-bfcb-8d222f5990e1@gmail.com \
--to=alx.manpages@gmail.com \
--cc=jlayton@kernel.org \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=neilb@suse.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