> see if I can chat with the concerned people The concerned people quit and now I'm left supporting their untested, undocumented, unreviewed code that doesn't

> see if I can chat with the concerned people The concerned people quit and now I'm left supporting their untested, undocumented, unreviewed code that doesn't have commit messages more meaningful that "now it works", "fix it", "make it work", "another try". So now answering every "why?" question takes me much longer than if the damn code was just documented in the first place. I often go back to my own code, go to make a change, can't remember why I did it a particular way, run "git blame, git show" and thank myself for having the foresight a year ago to spent an extra minute or two when the code was fresh in my mind writing down why I did something a particular way. If that doesn't float your boat, fine, but I don't want to work with you. The git repo itself is the epitome of what I aim for in my commit messages. Here's an example: https://github.com/git/git/commit/d3775de0745c975e2d13819a630757b2bbb673c3 https://github.com/git/git/commit/d3775de0745c975e2d13819a63... Literally a single line change, the addition of: BASIC_CFLAGS += -O0 to the top level Makefile, and 9 paragraphs of explanation in the commit message.