Git commit accepts several message flags (-m) to allow multiline commits

Re:Git commit accepts several message flags (-m) to allow mu... by seventh-chord on Wednesday July 08, 2020 @07:11AM (#23768749)

I guess "not nonsensical" would be more appropriate than "informative" :)

I tend to dump information like that in "// NB (my name, current date) tralala"-style comments. Do you have git integrated in your editor so you have git-blame-style commit messages next to your code? If that is the case, I guess putting the information in the commit messages makes sense.

Maybe it just comes down to how we choose to store auxiliary information.

[ Parent | on HN ]

Re:Git commit accepts several message flags (-m) to allow mu... by masklinn on Wednesday July 08, 2020 @07:20AM (#23768807)

> I tend to dump information like that in "// NB (my name, current date) tralala"-style comments. Do you have git integrated in your editor so you have git-blame-style commit messages next to your code? If that is the case, I guess putting the information in the commit messages makes sense.

No but blame is very close by and easy to access, so when I want to know why something was done that way it's not far away.

Comments keep getting out of sync, code gets inserted before or after, … and after a few years (or months on large codebases) it's just complete nonsense. I reserve them for stuff that's really super important to say right here (and todos).

[ Parent | on HN ]

Re:Git commit accepts several message flags (-m) to allow mu... by jfkebwjsbx on Wednesday July 08, 2020 @08:21AM (#23769148)

No, commit messages are not meant for "auxiliary information", but for giving the reasoning behind a change.

[ Parent | on HN ]