> > I imagine that this case is useful because of usual work interruptions > > in software development. A developer tries to bring various tasks > > forward in parallel. Branches will be switched often with unfinished > > work that needs to be kept before the reactivation of another task. > Aren't this and similar statements based on a general problem of people being afraid to commit, because CVS/SVN taught them to be affraid? We are in progress of migrating from CVS to GIT and this is one of the things i'm desperately fighting with. In Git Commit doesn't equal Share (it does in CVS), so why not to commit and save your work in progress and switch branches painlessly? Thanks, Eugene -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html