And since you can’t actually know for sure how much of a piece of code (or commit message) was written by AI you don’t really have a choice, do you? As time goes on and more people try to learn programming using AI a bunch of them may end up picking up some of its stylistic stuff. And if the submitter uses proper kernel formatting standards, will you be able to tell?
Honestly, seeing people go from concern trolling to what I like to call _concern farming_ has been utterly disappointing.
_concern farming_ is when people build entire crops of concerns with no intent to do anything other than fertilize them.
https://www.youtube.com/watch?v=NnV_cWeoo5Q
I really like your concern farming, will be using it going forward.
I think he's very wrong on this, though.
But people will not stop bringing it up over and over again. They just had the kernel summit where it was discussed again.
I imagine he’s REALLY REALLY tired of people continuing to try to start it up again.
Given Linus’ stance that it’s just a tool, which makes sense as a position, it’s really odd to ban only that one tool especially when you know your ban is completely useless to “make a statement”.
Just interesting to see how different people handle these situations.
The combativeness is a feature, not a bug.
For reals though: Comparing AI to editors or compilers is a massive false equivalency.
He’s someone who should know the policy.
Linus agreed that the “assisted by“ tag that was invented for AI wasn’t working and it got removed. There was already discussion that lead to this.
So here he is, again (presumably), taking this patch series removing that tag to try to push the topic again. That kernel summit I mentioned was 6 days ago as I type. LWN reported this was talked about.
I’m sure Linus would ignore me (a nobody) posting. Or someone who has made a few patches over the years.
I think Pinchart is high enough in the rankings Linus felt this was needed, or maybe more likely couldn’t hold his frustration.
I can’t imagine how frustrated by and tired of this topic Linus must be.