Why Linus Torvalds Demands Clear Commit Messages in Linux 6.3

Linus Torvalds warned developers that merge requests without explanatory commit messages are considered garbage, emphasizing that clear log messages are essential for maintainable Linux kernel history as the 6.3 merge window progresses.

21CTO
21CTO
21CTO
Why Linus Torvalds Demands Clear Commit Messages in Linux 6.3

Linux 6.3’s merge window is open, and Linus Torvalds has already received a flood of pull‑requests, which are being processed in an orderly fashion.

However, Linus expressed strong dissatisfaction with the log messages of some submissions, stating: “I have said it before, and I need to repeat it: if you are too lazy to explain why a merge request exists, then by definition it is just a pile of garbage!”

Missing comments in merge requests anger Linus Torvalds

Linus believes that if a developer cannot clearly explain a merge request, they should not submit it; submitting without explanation is “producing garbage.” He stresses that every developer must remember this rule and include meaningful comments in the log messages.

Currently, merge requests lacking comments appear meaningless, and Linus finds them abhorrent because they clutter the code history and make it harder to read.

The final outcome of this merge is a fix for Linux 6.2, and developers are encouraged to provide clearer annotations for future submissions.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

Linuxbest practiceskernel-developmentcommit messages
21CTO
Written by

21CTO

21CTO (21CTO.com) offers developers community, training, and services, making it your go‑to learning and service platform.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.