• git clone -- similar to svn checkout into a new folder
• git checkout -- for changing the current branch
  
• git pull -- effectively the same as "svn update", xcept it gets the entire change history, not just the latest commit data
  
• git push [--force] -- for sending changes into the repository
  
• git fetch -- downloads stuff but doesn't apply it to the checkout copy
• git merge -- can be used to merge the remote data (in which case it's like svn update), or to merge from another branch
• git branch
• git add
• git commit
• git stash save/pop -- can be used to temporarily undo some changes, and be able to recover them afterward
• git status, git log, ... -- for getting info about the state of the repository and the uncommited changes
• ... and more I that I use less often

I do agree that it is a bit annoying that git has so much trouble pulling with local changes, and that is the one area where svn just simply works better. In every other aspect, I have come to like the "git way" more.

That said, I avoid commandline git as much as possible. I prefer to use TortoiseGit (in Windows, at home), or SourceTree (at work, where I use a mac, and SourceTree is probably the least shitty frontend for git).

I like to say, that for someone who knows Subversion, learning git starts by realizing that all the usual svn concepts, apply to git, just NOT with the remote repository. The svn-like commands work with the local repository clone, and then it has a separate command set for interacting with remotes. Of course it's not a 1:1 match, but it's a good starting point. If you are able to "catch" that, then learning how to work with git becomes a LOT easier.