*Checks Linux kernel email folder I haven't checked in ages.*

*Most recent message CCed to me is a submission that includes significant chunks my own code verbatim, including even comments, "authored" by a FDo CoC team member, with zero credit (not Co-developed-by, nothing).*

I guess I wasted my time being careful about authorship back when I was involved with the kernel people...

Not going to bother replying, last time I tried to argue about authorship I just got hostility and troll news cycles. They can have my code and do whatever they want with it.

@lina what's the date on that message?

Because the latest lore.kernel.org messages (2nd December) where you are CC'd have a "signed-off-by" line against your name. And it looks like the content was originally written by you in October?

@dijumx Patches 6 and 8 of that series are based on my code and lack attribution (patch 8 being *the* last and most recent email I was referring to).

I originally wrote all this like, years ago by now. I'm sure the submitter refactored it quite a bit but there's still major chunks of the original code left, including verbatim comments I wrote.

I know some previous patches in the series keep my name (not crediting me at all even though I literally authored that source file in the first place would be preposterous and make them look really bad) but it sure is conveniently careless to split off bits into separate commits and slap someone else's name on them...

Back when I was reworking Git history to submit parts of the legacy R4L tree, I was extremely careful to make sure everyone who touched the code was credited and all sign-offs were collected and carried over. It's really depressing to see that an X.Org BoD and FDo CoC member, who really should know better, just doesn't give a damn.

But then again, she signed off on onboarding an abuser and stalker into FDo and sending me a gaslighting email about it, so I know she doesn't give a damn.