mirror/pcottle.learnGitBranching
1
0
Fork 0
mirror of https://github.com/pcottle/learnGitBranching.git synced 2025-07-02 18:54:27 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix a bunch of typos, mostly punctuation.

Browse source 
Some changes in word choice.
This commit is contained in:
Don Kirkby 2014-02-01 19:13:31 -08:00
parent f952bd7061
commit d5dee08e01
14 changed files with 32 additions and 32 deletions
Download patch file Download diff file Expand all files Collapse all files

4
src/levels/remote/pullArgs.js
View file

@ -21,7 +21,7 @@ exports.level = {
"",
"Now that you know pretty much *everything* there is to know about arguments for `git fetch` and `git push`, there's almost really nothing left to cover for git pull :)",
"",
"That's because git pull at the end of the day is *really* just shorthand for a fetch followed by merging in whatever was just fetched. You can think of it as running git fetch with SAME arguments specified and then merging in *where* those commits ended up.",
"That's because git pull at the end of the day is *really* just shorthand for a fetch followed by merging in whatever was just fetched. You can think of it as running git fetch with the *same* arguments specified and then merging in *where* those commits ended up.",
"",
"This applies even when you use crazy-complicated arguments as well. Let's see some examples:"
]
@ -43,7 +43,7 @@ exports.level = {
"",
"`git fetch origin bar~1:bugFix; git merge bugFix`",
"",
"See? git pull is really just shorthand for fetch + merge, and all git pull cares about is where the commits ended up (the `destination` argument that it figures out during fetch)",
"See? git pull is really just shorthand for fetch + merge, and all git pull cares about is where the commits ended up (the `destination` argument that it figures out during fetch).",
"",
"Lets see a demo:"
]