Hi Konstantin,
the idea of using merge --squash comes from:
1. the need to have a clean history of the changes: the developer
that implements
something (e.g. a feature or a bugfix) on a topic branch could
have done it
creating several commits in her/his development branch, commits
that are not
interesting for the overall project. E.g. s/he could have
committed, then run some
tests, found bugs or improvements in the code, and then have
committed again.
This is relevant only for the developer.
2. the need to push only the binaries to reduce push time. A merge
without --squash
creates a commit merge that has as parents the topic and the
develop merge.
A push transfers all of them, including the commits on the
develop branch, that
contain the binaries.
-Angelo
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/git-users?hl=en.
