4 ms·

I'd rather have it and not need it than need it and not have it. Besides, squashing means the identity of the commits changes, doesn't it? So you can't merge

by Pxtl 8y ago

I'd rather have it and not need it than need it and not have it. Besides, squashing means the identity of the commits changes, doesn't it? So you can't merge the same branch into 2 different branches (like merging a bugfix into both the release branch and the trunk) while keeping the identity of the commits - then when you merge your release branch into your device branch you get wonky duplication of commits in the history. I notice that move detection seems to get messed up by squashing sometimes... But maybe I'm using Git wrong, which imho is the biggest flaw of Git - it's so flexible that there are so many ways to "use it wrong".

pm90 8y ago
> I'd rather have it and not need it than need it and not have it. But squash commits do let you locate the identity of the authors. You just have to look at the PR, where all the original commits are listed
yawaramin 8y ago
> I'd rather have it and not need it than need it and not have it. Yeah but again, have you ever needed it? Because you can say the exact same thing about preserving every sequence of backspaces, deletes, and key typings into an editor. But when was the last time you or anyone needed that level of granularity?