[wang_li]

IF the code someone writes deserves to be included in a project, they deserve to have their name attributed to that code. You acting like there is some threshold of code to submit before someone's authorship is recognized is weird.

[jacquesm]

When you submit a patch to LKML you propose a fix, and if your patch is properly formatted and cleanly merges without further changes then it may be included as is. Or it might be parked until that section gets worked on in a larger context. In no way should your expectation be that your submission will be included verbatim and that you will be registered in the gitlog unless the maintainer decides that it be so.

Note that you are talking about a project that is older than quite a few of the people on HN and that it pays off to know how such a project operates before attempting to contribute, more so if you plan to go nuclear about your expectations not being met.

Finally, and if you do go nuclear it helps if you don't materially misrepresent the interaction with the maintainer, who did not exactly ask for your contribution.

[wang_li]

We don't have to discuss what might happen. We have a specific instance of something happening. In this case someone submitted a patch, the patch with a 1 line change ended up in the kernel. There is no need to talk about maybes, contexts, or what ifs. The kernel maintainer took someone else's code and put it in the kernel under their own name.

[jacquesm]

https://elinux.org/images/0/06/Lca13-gregkh-I-dont-want-your...

[wang_li]

https://www.cutenessoverflow.com/cute-and-adorable-puppy-pic...

So?