This question assumes there\'s a \"blessed\" central repository that members of a team
The command hg pull --rebase
isn't exactly analogous to svn update
, but the result can be the same.
In Subversion, if you update your working copy you get the latest changes in the repository merged in with any local changes. So the files in your repository are up to date but you might still have uncommitted changes.
In Mercurial, hg pull --rebase
, will get the latest changes from the 'central repository' (or whatever repository you're pulling from) to update your repository then shuffle along your local commits. You'll still need an hg update
to make your working copy the same as your local repository.