Linux

5372 readers

29 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

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

182

Linus Torvalds Asks Kernel Developers To Write Better Git Merge Commit Messages (www.phoronix.com)

submitted 1 month ago by neme@lemm.ee to c/linux@programming.dev

21 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] leftytighty@slrpnk.net 5 points 1 month ago

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.