5 ms·
> It's one more command, but I find it helps me visualize exactly what I want to happen are you saying that git pull can produce some unwanted artifacts? (e.g
by rinchik 7y ago
> It's one more command, but I find it helps me visualize exactly what I want to happen
are you saying that git pull can produce some unwanted artifacts? (e.g. not do exactly what you want it to do?)
- lazulicurio 7y ago> are you saying that git pull can produce some unwanted artifacts? (e.g. not do exactly what you want it to do?) Not in the sense that git pull has unpredictable behavior, but I like being able to view the remote history and manually diff against my local branch if there are changes that have been made.
- jolmg 7y agoThough it's still better to do fetch when you want to compare first, pull outputs the ranges of commits that it's pulling for each branch, so you can just copy and paste that into a diff or log command, too. I say this because I used to just ignore the output, but then I found that it's useful, too. So, if git-pull outputs b3b2007..9bad624 master -> origin/master I can do `git diff b3b2007..9bad624` or `git log b3b2007..9bad624` to see what I just pulled.
- juped 7y agoDepends on your mental model. I think people expect something similar to CVS update at first, and then git surprises them by doing other things.
- rinchik 7y agoI don't think git can surprise though... git GUIs on the other hand can be a mystery.