From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Costa Shulyupin <costa.shul@redhat.com>,
linux-doc@vger.kernel.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux BPF <bpf@vger.kernel.org>
Subject: Re: [PATCH v3] Documentation: subsystem-apis: Categorize remaining subsystems
Date: Fri, 02 Jun 2023 04:19:10 -0600 [thread overview]
Message-ID: <87ilc6yxnl.fsf@meer.lwn.net> (raw)
In-Reply-To: <ZHm_s7kQP6kilBtO@debian.me>
Bagas Sanjaya <bagasdotme@gmail.com> writes:
> As you're still newbie here, I'd recommend you to try contributing to
> drivers/staging/ first in order to gain experience on kernel developement
> workflow. Also, you use your RedHat address, so I expect you have been
> given kernel development training from your company (and doesn't make
> trivial errors like these ones).
Bagas, please. I'll ask you directly: please don't go telling
documentation contributors how to comport themselves; you have plenty
enough to learn yourself on that front. It's hard enough to get
contributors to the documentation as it is without random people showing
up and giving orders.
I have distractions that are increasing my (already less than stellar)
latency, but I'll get to this stuff.
Thanks,
jon
next prev parent reply other threads:[~2023-06-02 10:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 8:55 [PATCH] docs: consolidate storage interfaces Costa Shulyupin
2023-05-30 8:54 ` Bagas Sanjaya
2023-05-31 10:17 ` [PATCH] docs: organize subsystems Costa Shulyupin
2023-06-01 3:13 ` Bagas Sanjaya
2023-06-01 14:55 ` [PATCH v3] Documentation: subsystem-apis: Categorize remaining subsystems Costa Shulyupin
2023-06-01 16:28 ` Randy Dunlap
2023-06-02 10:08 ` Bagas Sanjaya
2023-06-02 10:19 ` Jonathan Corbet [this message]
2023-06-02 12:33 ` Bagas Sanjaya
2023-06-09 8:05 ` Jonathan Corbet
2023-06-18 6:29 ` [PATCH v4] docs: consolidate storage interfaces Costa Shulyupin
2023-06-18 15:19 ` Randy Dunlap
2023-06-18 16:09 ` Costa Shulyupin
2023-06-21 15:33 ` Jonathan Corbet
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=87ilc6yxnl.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bagasdotme@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=costa.shul@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.