Re:Our beautiful fake histories
by HOLYCOWBATMAN on Friday July 10, 2015 @09:33PM
(#9868088)
>It's not about faking anything, it's a question of what information you want to leave for posterity
Exactly, i bet when this guy wrote his blog post he used backspace more than once. No idea why he thinks git is any different.
I commit all kind of garbage while developing: stackoverflow references, commented code examples, temp commits when i have to leave in a hurry, etc... rebasing --interactive + merge (with optional no-ff if you hate linear history) is a must and basic respect for your colleagues.
You can cook naked if you want but i dont want to see your pubes in my meal.
It's not about faking anything, it's a question of what information you want to leave for posterity. And frankly I come down pretty strongly against preserving warts for warts sake. As a rule of thumb, commits should be as fine-grained as possible without breaking the build. In my experience more detail than that gives diminishing returns in utility as the signal-to-noise ratio drops and you get overwhelmed with details which only represent a brain fart on the part of the developer, and never had any measurable impact on the project.