Here are my thoughts:

Pro for using squashes:
* it may be easier to revert commits and the timeline looks much consistant
in a way that "feature" / "bugfix" commits are listed as once and are not
listed when the steps (single commits) are listed when they happened
* easier to merge "complete" features between branches (backport) without
forgetting single commits that may be required.

A con could be if people working together on a feature (that may exists
longer) the committer who merges (and squashes) the commits is listed e.g.
using "git blame". This may hide all origin contributors while they are
still listed in the squash message

1+ for squashing commits if a single commiter was working on that branchm
otherwise I would suggest to avoid squasing to keep who has commited which
lines

--
Cheers Frank
------------------------------------------------------------------------------
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to