> gerrit works pretty much the same way (but also forces you to squash changes into a single commit) That may explain why one of the committers I work with on

> gerrit works pretty much the same way (but also forces you to squash changes into a single commit) That may explain why one of the committers I work with on an open source project heavily suggests squashing changes into a single commit when merging topic branches into master. He works with gerrit at his day job! Personally, I think it's better to only squash experimental commits or minor stuff like removing a newline, and to keep development of a feature spread out over several commits if it makes sense. Makes it easier to revert back to a specific commit.