2 ms·
I wrote a few similar commit messages - mainly upon merges, but sometimes when commiting small, but important changes too. The result: I was ridiculed and laugh
by klibertp 14y ago
I wrote a few similar commit messages - mainly upon merges, but sometimes when commiting small, but important changes too. The result: I was ridiculed and laughed at... I even seem to remember that someone said I was "unfulfilled writer" (believe me, in my language that was much more unpleasant...).
I can't help but think that majority of programmers are just illiterate and they feel threatened when someone actually has the will (as you can probably see from this post my skill isn't all that great either) to write...
- fexl 14y agoYes, I could have let it slide and simply written "Fixed bug in type_open propagation in parse.c". But I sort of wanted to "punish" myself a little and force myself to write out precisely what I had done wrong in painfully explicit terms. Otherwise, as Brian Griffin said to Peter, I "wouldn't learn anything." ;)
- masklinn 14y ago> The result: I was ridiculed and laughed at... Well fuck these people, I for one am sick and tired of looking for why a code section was changed in ways I don't understand in the log or blame and getting "changed stuff" back. I'd much rather people explained clearly (and verbosely if needed) what the bloody hell they're committing this change for.
- Evbn 14y agoMaybe it would help to put design docs somewhere more accessible than buried in the commit log.