Hi, > NO, that's the opposite
Really? https://wincent.com/wiki/git_rebase:_you're_doing_it_wrong Dozen of stack overflow question on the issue which warn about rebasing. For instance: http://stackoverflow.com/questions/8939977/git-push-rejected-after-feature-branch-rebase "Rebase and a shared repository generally do not get along. This is rewriting history. If others are using that branch or have branched from that branch then rebase will be quite unpleasant." http://stackoverflow.com/questions/457927/git-workflow-and-rebase-vs-merge-questions "It really kills me that people are recommending a rebase workflow as a better alternative to a merge workflow for conflict resolution" "With rebase, there is no undo!" Also http://git-scm.com/book/en/Git-Branching-Rebasing#The-Perils-of-Rebasing Again I'll ask do we really want this option to be the default? Justin
