penguin_booze 2 days ago | parent | next [-]

I wish developers--new and old alike--pay attention to the commit messages that goes into the kernel. Granted, it takes a subject matter expert to really understand what's being said, but the general format and layout of commit messages is instructive. Commit messages helps the reader/reviewer get their bearings; they also help to build the case from the bottom up.

The fact that the development team is globally distributed both necessitates this kind of knowledge serialization and preserves it for posterity. It's completely different from tapping a colleague sitting next you on the shoulder, and saying "psst, can you approve this quick? It's just a bunch of fixes".

	▲	andrybak 9 hours ago \| parent [-]
		The kernel repository has pretty extensive documentation on how to describe the code changes in the commit messages: - https://docs.kernel.org/process/submitting-patches.html#desc... - https://github.com/torvalds/linux/blob/master/Documentation/... - https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin... Git's own guidelines also have a nice description on how to write a better commit message: - https://git-scm.com/docs/SubmittingPatches - https://github.com/git/git/blob/master/Documentation/Submitt... - https://git.kernel.org/pub/scm/git/git.git/tree/Documentatio...

▲

andrybak 4 hours ago | parent | prev [-]

A different UI to the mailing list with the whole thread on one page and diff coloring, if anyone is interested: https://lore.kernel.org/lkml/20250319-rfc2203-seqnum-cache-v...