There are two different philosophies of branches as near as I can make out. * Branches as 'records of effort'/'who did what when on what project'. * Separatin

There are two different philosophies of branches as near as I can make out. * Branches as 'records of effort'/'who did what when on what project'. * Separating lines of development to keep mainline builds from falling over. In a 'audit-thy-process' environment, immutable history and records of projects have a high importance. If the goal is 'simply' to separate lines of development - well then you can squash commits and it doesn't matter.