Git forges
Git forges
Posted Oct 17, 2025 15:18 UTC (Fri) by marcH (subscriber, #57642)In reply to: Git forges by pizza
Parent article: Large language models for patch review
In projects with "modern" development practices, developers and CI use the same test and automation code and configurations everywhere possible. No duplication and no "CI secret". Everyone can push the same buttons. They don't always have to, but they easily can whenever they want to. Running any check is as simple as running checkpatch.pl.
In projects lagging years or even decades behind, everyone and everything has their custom, personal scripts and private configuration files. The level of duplication there is probably the simplest and best metric of project (im)maturity.
One of the interesting side effects of this duplication is: the very frequent inability to reproduce bugs - even the ones with a 100% reproduction rate.
To be fair: there is a quite wide maturity range across kernel subsystems and there are some heroic efforts like 0day to cope with the "email-based database"[*] submission process. But the average does not look great and the lowest look even worse. So, "AI code reviews" really sounds like "cart before the horse". But... new shiny?
[*] speaking of development immaturity, don't get me started on recently killing "Link:" = the only, limited alternative to a proper Change-Id:... I digress.
The LWN site is currently under high scraper load, so comment display has been suppressed for anonymous users. If you are a human, you may read the comments by clicking the button below:
Note: you can avoid this step in the future by logging into your LWN account.