Revisions to What is the difference between 'git pull' and 'git fetch'?

grammar, removal of '...' in answer especially considering the possible confusion with it being git diff syntax, and usage of 'double/triple dot' as the explicit code samples (.. and ...) are enough

Source Link

edit approved Dec 18, 2024 at 7:23

jonathanh

342
5
11

One use case of git fetch is that the following will tell you about any changes in the remote branch since your last pull... so you can check before doing an actual pull, which could change files in your current branch and working copy.

git fetch
git diff ...origin

See git diff documentation regarding the double- .. and triple-dot ... syntax.

One use case of git fetch is that the following will tell you any changes in the remote branch since your last pull... so you can check before doing an actual pull, which could change files in your current branch and working copy.

git fetch
git diff ...origin

See git diff documentation regarding the double- .. and triple-dot ... syntax.

One use case of git fetch is that the following will tell you about any changes in the remote branch since your last pull so you can check before doing an actual pull, which could change files in your current branch and working copy.

git fetch
git diff ...origin

See git diff documentation regarding .. and ... syntax.

Reword.

Source Link

edited Jul 10, 2022 at 22:53

Mateen Ulhaq

28.1k
22
122
157

One use case of git fetch is that the following will tell you any changes in the remote branch since your last pull... so you can check before doing an actual pull, which could change files in your current branch and working copy.

git fetch
git diff ...origin

See: https://git-scm.com/docs/git-diffgit diff documentation regarding the double- .. and triple-dot ... syntax in the diff command.

One use case of git fetch is that the following will tell you any changes in the remote branch since your last pull... so you can check before doing an actual pull, which could change files in your current branch and working copy.

git fetch
git diff ...origin

See: https://git-scm.com/docs/git-diff regarding double- and triple-dot syntax in the diff command

One use case of git fetch is that the following will tell you any changes in the remote branch since your last pull... so you can check before doing an actual pull, which could change files in your current branch and working copy.

git fetch
git diff ...origin

See git diff documentation regarding the double- .. and triple-dot ... syntax.

Added link to explain syntax

Source Link

edit approved Jul 16, 2019 at 19:49

rkedge

561
4
12

One use case of git fetch is that the following will tell you any changes in the remote branch since your last pull... so you can check before doing an actual pull, which could change files in your current branch and working copy.

git fetch
git diff ...origin

See: https://git-scm.com/docs/git-diff regarding double- and triple-dot syntax in the diff command

One use case of git fetch is that the following will tell you any changes in the remote branch since your last pull... so you can check before doing an actual pull, which could change files in your current branch and working copy.

git fetch
git diff ...origin

One use case of git fetch is that the following will tell you any changes in the remote branch since your last pull... so you can check before doing an actual pull, which could change files in your current branch and working copy.