From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Mathnerd314 <mathnerd314.gph@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: EINTR for fsync(2)
Date: Tue, 1 Feb 2022 15:36:54 +0100 [thread overview]
Message-ID: <e43bf747-a486-749c-3171-39dddb6250c2@gmail.com> (raw)
In-Reply-To: <CADVL9rH+4ptFTnJwD7u5b=j-H7VkOaya7Cd49EdhxPNH-6=T6w@mail.gmail.com>
Hi Mathnerd314,
On 2/1/22 00:17, Mathnerd314 wrote:
> On Mon, Jan 31, 2022 at 1:44 PM Alejandro Colomar (man-pages)
> <alx.manpages@gmail.com> wrote:
>>
>> Mathnerd314: Thanks for the report! It's useful to CC the relevant
>> kernel developers when reporting non-trivial bugs such as this one.
>> They know better than we do. :)
>
> Ah, but then I would have had to know that this is a non-trivial
> question, as opposed to a 2-line patch.
It's very subjective. But when it's a technical bug about very specific
knowledge, they know better than us. When it's a typo or a formatting
issue in the manual page, it's trivial. ;)
> And CC'ing kernel developers
> is not mentioned on
> https://www.kernel.org/doc/man-pages/reporting_bugs.html.
Hmm, yes, I should fix that. Thanks!
>
> Oh well, there's always next time.
Yup, don't worry, I meant it for next time. Anyway, it's easy for me to
add them to the CC if you don't or forget.
>
> -- Mathnerd314
Cheers,
Alex
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2022-02-01 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 18:32 EINTR for fsync(2) Mathnerd314
2022-01-31 20:44 ` Alejandro Colomar (man-pages)
2022-01-31 23:17 ` Mathnerd314
2022-02-01 14:36 ` Alejandro Colomar (man-pages) [this message]
2022-02-01 0:30 ` Matthew Wilcox
2022-02-01 14:48 ` Alejandro Colomar (man-pages)
2022-02-01 19:56 ` Mathnerd314
2022-02-01 20:32 ` Matthew Wilcox
[not found] ` <CADVL9rF8chZpN9Nycs=MW0JuppnFaoq07gjS+ODC3CSUt0w1xA@mail.gmail.com>
2022-02-03 17:33 ` Fwd: " Mathnerd314
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=e43bf747-a486-749c-3171-39dddb6250c2@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mathnerd314.gph@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