> Squashing & rebasing instead of merging is the latest fashion. I'm not a > fan of these bell bottomed pants. > Squashing eliminates the history of what actually happened, in particular, > it's hard to tell > if an earlier comment was acted on if you eliminate the history through > squashing. > You also can't tell what "really happened". > Still, rebasing might be a good option for a single maintainer who feels strongly about what should be included in the history of their project. After approving changes they are no more interested in all the clutter and dirty details.
But for most people it doesn't matter what a particular git workflow is as long as it establishes some order. -- You received this message because you are subscribed to the Google Groups "Metamath" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/metamath/014b41f4-e8c2-4773-9f57-db48422593fbn%40googlegroups.com.
