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.

[–] Crackhappy@lemmy.world 3 points 2 years ago (1 children)

Trying to figure out if that typo was intent9ional or not.

[–] plz1@lemmy.world 2 points 2 years ago

Nope I'm just awful.

[–] XTL@sopuli.xyz 2 points 1 year ago

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.

[–] funkless_eck@sh.itjust.works 6 points 2 years ago* (last edited 2 years ago) (1 children)

You change some code and send it in, you add a cover letter explaining what you did and why. The Linux guy wants you to write more detailed cover letters when you do.

edit: wrote this before reading the article. he actually just wants people to write using active voice instead of passive.

[–] Brahvim@lemmy.kde.social 1 points 2 years ago

Aww, more personalized COMMITMSGs?!...

That's wholesome.