From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
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, 2 Jun 2023 19:33:42 +0700 [thread overview]
Message-ID: <1f66d945-4f3f-6f8e-2d14-38167c0a0759@gmail.com> (raw)
In-Reply-To: <87ilc6yxnl.fsf@meer.lwn.net>
On 6/2/23 17:19, Jonathan Corbet wrote:
> 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.
>
Hi jon, thanks for another tip. I also learn contributing patches the
hard way by being rejected (honestly sometimes I learn, sometimes I
don't).
Let me clarify the situation. Previously in v2, I reviewed Costa's patch
by replying with proposing my own version, keeping patch author intact.
There, I categorized a few more items while sorting all of them. I
treated it as minor fixup that was attributed by brackets in the
SoB area (I could also use Co-developed-by: for this purpose too).
Then, Costa rerolled v3 using my version, but the From: address
in the patch message is mine without corresponding SoB, hence when you
apply his v3, there would be author mismatch (commit author is me
yet different SoB from him). I expected that my proposal in v2 is
carried by him (and also have SoB from both me and him as the sender
who carried my patch).
> I have distractions that are increasing my (already less than stellar)
> latency, but I'll get to this stuff.
>
I'm too, because I'm AuDHD and I can (and do) easily distracted; living
in a paradox between routine fixation and desire for quick action :).
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-06-02 12:33 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
2023-06-02 12:33 ` Bagas Sanjaya [this message]
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=1f66d945-4f3f-6f8e-2d14-38167c0a0759@gmail.com \
--to=bagasdotme@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).