- It is also common to recusively add all files in a new project by specifying
+ It is also common to recursively add all files in a new project by specifying
the current working directory like this: git add .. Since Git
will recursively add all files under a directory you give it, if you give it
the current working directory, it will simply start tracking every file
diff --git a/index.html b/index.html
index 03837da..ba22a53 100644
--- a/index.html
+++ b/index.html
@@ -98,7 +98,7 @@ layout: reference
how they differ or pull content out of them, etc.
If you think about Git diff --git a/remotes/index.html b/remotes/index.html index 2720553..394874c 100644 --- a/remotes/index.html +++ b/remotes/index.html @@ -15,9 +15,9 @@ layout: reference so far have been done locally, just updating a local database. To collaborate with other developers in Git, you have to put all that data on a server that the other developers have access to. The way Git - does this is to syncronize your data with another repository. There + does this is to synchronize your data with another repository. There is no real difference between a server and a client - a Git repository - is a Git repository and you can syncronize between any two easily. + is a Git repository and you can synchronize between any two easily.
Once you have a Git repository, either one that you set up on your @@ -54,12 +54,12 @@ layout: reference
Unlike centralized version control systems that have a client that is very different from a server, Git repositories are all basically equal and - you simply syncronize between them. This makes it easy to have more than + you simply synchronize between them. This makes it easy to have more than one remote repository - you can have some that you have read-only access to and others that you can write to as well.
So that you don't have to use the full URL of a remote repository every
- time you want to syncronize with it, Git stores an alias or nickname for
+ time you want to synchronize with it, Git stores an alias or nickname for
each remote repository URL you are interested in. You use the
git remote command to manage this list of remote repos that
you care about.
Git has two commands to update itself from a remote repository.
- git fetch will syncronize you with another repo, pulling down any data
+ git fetch will synchronize you with another repo, pulling down any data
that you do not have locally and giving you bookmarks to where each branch on
- that remote was when you syncronized. These are called "remote branches" and are
+ that remote was when you synchronized. These are called "remote branches" and are
identical to local branches except that Git will not allow you to check them out -
however, you can merge from them, diff them to other branches, run history logs on
- them, etc. You do all of that stuff locally after you syncronize.
+ them, etc. You do all of that stuff locally after you synchronize.
The second command that will fetch down new data from a remote server is @@ -238,11 +238,11 @@ From github.com:schacon/hw
If you have more than one remote repository, you can either fetch from specific
- ones by running git fetch [alias] or you can tell Git to syncronize
+ ones by running git fetch [alias] or you can tell Git to synchronize
with all of your remotes by running git fetch --all.
- In a nutshell you run git fetch [alias] to syncronize your
+ In a nutshell you run git fetch [alias] to synchronize your
repository with a remote repository, fetching all the data it has that you do
not into branch references locally for merging and whatnot.