On 6/2/23 17:19, Jonathan Corbet wrote: > Bagas Sanjaya <bagasdotme@xxxxxxxxx> 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
