Why do I need hg update after hg pull while in git I'm doing only git pull

In git to pull and use the latest changes to my local repository I’m using git pull.

In hg, I also use hg pull but it prints then

run ‘hg update’ to get a working copy

I do run hg update but I wonder why is this difference from git?

  • How to use Hg-to-Git tool - fast-export?
  • Version control system for game development with UDK?
  • Managing release branches in Mercurial
  • Versioning machine specific configs
  • How do I git reset --hard HEAD on Mercurial?
  • Ensuring a merge between branches happens in one direction
  • Mercurial repository layout for multiple branches
  • How do I clone/pull from GitHub, but push to Kiln?
  • 3 Solutions collect form web for “Why do I need hg update after hg pull while in git I'm doing only git pull”

    The other answers don’t actually answer the question, which is: why don’t Git and Mercurial work the same? Is there a philosophical difference?

    In Mercurial, pull is the opposite of push: it syncs the local repo with a remote repo without touching the working copy. So it’s more consistent.

    In Git, pull is a fetch plus a merge, or a pull plus an update in Mercurial terms. Usually this is what you want. So it’s more efficient.

    The Distributed Version Control University talk has a slide at the 4-minute mark that clearly demonstrates the way Mercurial works. Michael Ernst’s Version control concepts and best practices has a similar diagram (included below):

    Distributed version control

    Because git pull internally performs git fetch and git merge, whereas hg pull only does what git fetch does. Just do hg pull -u instead. See also this command equivalence table.

    To get equivalent git functionality enable the fetch Mercurial extension (bundled with Mercurial distributions), see fetch extension. It will execute a hg pull -u.

    Git Baby is a git and github fan, let's start git clone.