Bill Wohler
2016-01-10 23:06:48 UTC
Hey folks,
I'd like to propose that in either Git repository, we use git fetch
followed by git merge --ff-only in lieu of git pull. This can also be
accomplished with git pull --ff-only. If the latter fails due to local
commits, then git rebase --preserve-merges can be used.
I like to do this to reduce the number of spurious merge commits.
Intentional merge commits to document a developmental path are, of
course, fine.
The fetch also lets you first perform a diff with origin to see what has
changed since that may suggest a preference for merge or rebase.
I use the --preserve-merges since rebase will flatten any explicit
feature branches you have without it.
How does this sound?
If you prefer the spurious merge commits, please explain why and we can
discuss.
Thanks.
I'd like to propose that in either Git repository, we use git fetch
followed by git merge --ff-only in lieu of git pull. This can also be
accomplished with git pull --ff-only. If the latter fails due to local
commits, then git rebase --preserve-merges can be used.
I like to do this to reduce the number of spurious merge commits.
Intentional merge commits to document a developmental path are, of
course, fine.
The fetch also lets you first perform a diff with origin to see what has
changed since that may suggest a preference for merge or rebase.
I use the --preserve-merges since rebase will flatten any explicit
feature branches you have without it.
How does this sound?
If you prefer the spurious merge commits, please explain why and we can
discuss.
Thanks.
--
Bill Wohler <***@newt.com> aka <***@nasa.gov>
http://www.newt.com/wohler/
GnuPG ID:610BD9AD
Bill Wohler <***@newt.com> aka <***@nasa.gov>
http://www.newt.com/wohler/
GnuPG ID:610BD9AD