> people rarely make fine grained enough commits to be able to target specific lines or blocks Take your own advice then: don't hire such people. Why would you

> people rarely make fine grained enough commits to be able to target specific lines or blocks Take your own advice then: don't hire such people. Why would you insist on maintaining documentation and not maintaining a reasonable change log in your commits, if knowing "why" is important to you? (I make the advice tongue-in-cheek btw. Better to educate and lift developers up wherever you can than just freeze them out. Not everyone has the experience with these things that we do.) There's not a one-size-fits-all solution here. Different orgs handle their code history different ways, but having tasted the power Git gives you over certain other VCSes to make the commit log really useful as a record of change, and having taken advantage of that feature several times myself, I wouldn't want to go back. This follows another comment I just made on the topic: https://news.ycombinator.com/item?id=23743973 https://news.ycombinator.com/item?id=23743973