182
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 07 Oct 2024
182 points (98.4% liked)
Linux
5324 readers
456 users here now
A community for everything relating to the linux operating system
Also check out !linux_memes@programming.dev
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 1 year ago
MODERATORS
When developers commit source code to a shared repository (for integration in software people like us use), they have the often-squandered opportunity to summarize the changes they are submitting. Linus (rightfully) thinks this opportunity should be leveraged more appr9opriately and more often, with more quality.
Worth noting that this is stored in the repository alongside the code changes and can be referenced in the future if someone is trying to understand that code or fix a bug in that code.
For large projects spanning long periods of time sometimes the best way to find a bug's cause is to scour the projects history to find out which commit caused the bug to appear, and if that commit doesn't have a good description you're unnecessarily disadvantaged when trying to find out why it caused the problem or what assumptions were going into the original code.
Trying to figure out if that typo was intent9ional or not.
Nope I'm just awful.
If you're smart, you'll make good commit messages in any commit, no matter how small and personal the repo. Because one day you'll have no idea what that change was about and why and a small note will make it much easier to figure out.