AI-Generated · anthropic/claude-sonnet-5.5 via openrouter/openrouter/auto-beta; researched by moonshotai/kimi-k2-0905

Linux 7.4 Merge Window Sets a Kernel Record With 19,671 Commits

Linus Torvalds released Linux 7.4-rc1 after the largest merge window in kernel history, and he credits AI-assisted fixes arriving earlier in the cycle.

Linus Torvalds tagged Linux 7.4-rc1 on November 1, 2026, closing what Phoronix describes as the largest merge window in kernel history, with 19,671 commits. The figure nearly matches the entire commit volume of the previous record-setting 7.3 development cycle, which means a window of roughly two weeks carried close to a full cycle’s worth of work.

The scale stands out against the baseline. The Register reports that the release carried almost 20,000 commits, compared with the usual figure of around 15,000. That is a jump of roughly a third over a typical merge window for the Linux kernel, a project whose release rhythm has been steady enough that maintainers plan around it.

Torvalds attributes much of the surge to AI and LLM activity. Phoronix notes that he tied the unusual volume to AI-driven tooling producing patches and fixes at a rate the merge window had not previously absorbed, rather than to any single large feature or subsystem rewrite.

What he said about timing matters as much as the count. According to The Register, Torvalds said he is “much happier” with AI fixes landing during the merge window instead of piling up during the stabilization phase, and he called this a “much healthier model.” The headline also describes the kernel as out of its “stabilization phase,” a reference to the period in which AI-generated fixes had been arriving after the merge window had closed.

The distinction is a practical one. The kernel’s process reserves the merge window for new code and the release-candidate period for fixing regressions. A flood of automated fixes arriving late in the cycle strains that second phase, because every patch still needs human review from maintainers who are trying to converge on a release. Moving the same volume into the merge window puts it where the process expects large changes, and where there is time for them to be tested across several release candidates.

The sources do not say how many of the 19,671 commits were AI-generated, and neither quantifies the share, so the record’s exact composition remains unclear. They also leave open whether the volume will hold. A single window cannot show whether this is a new steady state or a backlog clearing, and the 7.4 release candidates will be the first test of how well review capacity keeps up. For now, the project’s lead is describing the larger flow as an improvement in process rather than a problem to be contained.

Sources