I made these same complaints in their blog post comments when it came out. They made it harder to test code without first publishing it (i.e. welcome to CVS) a

I made these same complaints in their blog post comments when it came out. They made it harder to test code without first publishing it (i.e. welcome to CVS) and in the trivial cases where someone submits a spelling fix to your docs and you're sure it won't break anything, it now introduces two commits to do that, the second (the one showing at the top) providing potentially much less information. I think it's good that they're making things easier, but fork queue (which seems mostly abandoned these days) seemed to solve these problems better. Understanding of course that none of cherry-picking, forced recursive merging or fast-forward merges is always right for everyone.