> A complete and utter waste of time. You spend more time messing about with rebase than solving problems. That can be avoided by only staging and committing c

> A complete and utter waste of time. You spend more time messing about with rebase than solving problems. That can be avoided by only staging and committing changes when the change is actually completely implemented. For example, I'll make a change and then I'll stage it as follows: 1. Stage and commit a new method and associated unit tests 2. Stage and commit calls to the new method 3. Stage and commit the version update Having to go through extensive rebasing is really an issue with treating version control as a back up system rather than a way to record individual units of work with well crafted commit messages that describe what and why the change was made.