14 ms·
I like going through Postgres's commit logs once in a while for exactly that reason, non-trivial commits (logic wise, they may be a 1LOC commit) get short-story
by masklinn 10y ago
I like going through Postgres's commit logs once in a while for exactly that reason, non-trivial commits (logic wise, they may be a 1LOC commit) get short-story-scale messages, often with references to ML thread(s) where the issue or change was discussed. It's a nice change of pace from $dayjob where a commit changing half the codebase in ways unspecified gets logged as "improvements".
- koolba 10y ago> It's a nice change of pace from $dayjob where a commit changing half the codebase in ways unspecified gets logged as "improvements". The best (worst?) one is where you'll see a series of major changes with the following commit messages: - Add feature X (no explanation of what it does) - Fix feature X - Really fix feature X - Fix feature X for real - Finally fixed X - Fix test environment
- masklinn 10y agoI know you don't work at $dayjob because the last commit would be "fix X test which is dumb", which removes the test entirely.