Merge remote-tracking branch 'origin/master' into chapter-7

Conflicts:
	book/07-git-tools/1-git-tools.asc

Author: ben

OUTLINE.txt

@@ -42,14 +42,6 @@
     * Limiting Log Output
     * Using a GUI to Visualize History
 2.4 Undoing Things
-    * Reset Demystified
-      * The Three Trees
-      * The Workflow
-      * The Role of Reset
-      * Reset With a Path
-      * A Fun Example
-      * Check It Out
-      * Summary
     * Changing Your Last Commit
     * Unstaging a Staged File
     * Unmodifying a Modified File
@@ -88,7 +80,7 @@
     * Topic Branches
 3.5 Remote Branches
     * Pushing
-    * Tracking Branches
+    * Tracking / Upstream Branches
     * Deleting Remote Branches
 3.6 Rebasing
     * The Basic Rebase
@@ -111,16 +103,7 @@
 4.4 Setting Up the Server
 4.5 Public Access
 4.6 GitWeb
-4.9 Git Daemon
-4.8 Gitolite
-    * Installing
-    * Customising the Install
-    * Config File and Access Control Rules
-    * Advanced Access Control with "deny" rules
-    * Restricting pushes by files changed
-    * Personal Branches
-    * "Wildcard" repositories
-    * Other Features
+4.7 Git Daemon
 4.X GitLab
 4.X Gerrit
 4.10 Other Hosting Options (bitbucket, stash, kiln, etc.)
@@ -198,14 +181,19 @@ X.X Summary
       * Double Dot
       * Multiple Points
       * Triple Dot
-6.2 Interactive Staging
-    * Staging and Unstaging Files
-    * Staging Patches
-6.3 Stashing
+6.3 Stashing and Cleaning
     * Stashing Your Work
     * Un-applying a Stash
     * Creating a Branch from a Stash
+    * Git Clean
 6.X Searching (git grep)
+6.2 Interactive Staging
+    * Staging and Unstaging Files
+    * Staging Patches
+6.X Git Reset
+    * The Three Trees of Git
+    * Reset with a path
+    * Reset vs Checkout
 6.4 Rewriting History
     * Changing the Last Commit
     * Changing Multiple Commit Messages

book/01-introduction/1-introduction.asc

@@ -1,3 +1,4 @@
+[[_getting_started]]
 == Getting Started
 
 This chapter will be about getting started with Git.
@@ -6,7 +7,7 @@ At the end of this chapter you should understand why Git is around, why you shou
 
 === About Version Control (((version control)))
 
-What is ((("version control"))), and why should you care?
+What is "version control", and why should you care?
 Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later.
 For the examples in this book you will use software source code as the files being version controlled, though in reality you can do this with nearly any type of file on a computer.
 
@@ -34,7 +35,7 @@ RCS works by keeping patch sets (that is, the differences between files) in a sp
 
 The next major issue that people encounter is that they need to collaborate with developers on other systems.
 To deal with this problem, Centralized Version Control Systems (CVCSs) were developed.
-These systems, such as CVS, Subversion, and Perforce, have a single server that contains all the versioned files, and a number of clients that check out files from that central place.
+These systems, such as CVS, Subversion, and Perforce, have a single server that contains all the versioned files, and a number of clients that check out files from that central place. (((CVS)))(((Subversion)))(((Perforce)))
 For many years, this has been the standard for version control.
 
 .Centralized version control.
@@ -67,19 +68,19 @@ This allows you to set up several types of workflows that aren’t possible in c
 
 As with many great things in life, Git began with a bit of creative destruction and fiery controversy.
 
-The Linux kernel is an open source software project of fairly large scope.
+The Linux kernel is an open source software project of fairly large scope.(((Linux)))
 For most of the lifetime of the Linux kernel maintenance (1991–2002), changes to the software were passed around as patches and archived files.
-In 2002, the Linux kernel project began using a proprietary DVCS called BitKeeper.
+In 2002, the Linux kernel project began using a proprietary DVCS called BitKeeper.(((BitKeeper)))
 
 In 2005, the relationship between the community that developed the Linux kernel and the commercial company that developed BitKeeper broke down, and the tool’s free-of-charge status was revoked.
-This prompted the Linux development community (and in particular Linus Torvalds, the creator of Linux) to develop their own tool based on some of the lessons they learned while using BitKeeper.
+This prompted the Linux development community (and in particular Linus Torvalds, the creator of Linux) to develop their own tool based on some of the lessons they learned while using BitKeeper.(((Linus Torvalds)))
 Some of the goals of the new system were as follows:
 
 *  Speed
 *  Simple design
 *  Strong support for non-linear development (thousands of parallel branches)
 *  Fully distributed
-*  Able to handle large projects like the Linux kernel efficiently (speed and data size)
+*  Able to handle large projects like the Linux kernel efficiently (speed and data size)(((Linux)))
 
 Since its birth in 2005, Git has evolved and matured to be easy to use and yet retain these initial qualities.
 It’s incredibly fast, it’s very efficient with large projects, and it has an incredible branching system for non-linear development (See <<_git_branching>>).
@@ -89,7 +90,7 @@ It’s incredibly fast, it’s very efficient with large projects, and it has an
 So, what is Git in a nutshell?
 This is an important section to absorb, because if you understand what Git is and the fundamentals of how it works, then using Git effectively will probably be much easier for you.
 As you learn Git, try to clear your mind of the things you may know about other VCSs, such as Subversion and Perforce; doing so will help you avoid subtle confusion when using the tool.
-Git stores and thinks about information much differently than these other systems, even though the user interface is fairly similar, and understanding those differences will help prevent you from becoming confused while using it.
+Git stores and thinks about information much differently than these other systems, even though the user interface is fairly similar, and understanding those differences will help prevent you from becoming confused while using it.(((Subversion)))(((Perforce)))
 
 ==== Snapshots, Not Differences
 
@@ -138,7 +139,7 @@ This means it’s impossible to change the contents of any file or directory wit
 This functionality is built into Git at the lowest levels and is integral to its philosophy.
 You can’t lose information in transit or get file corruption without Git being able to detect it.
 
-The mechanism that Git uses for this checksumming is called a SHA-1 hash.
+The mechanism that Git uses for this checksumming is called a SHA-1 hash.(((SHA-1)))
 This is a 40-character string composed of hexadecimal characters (0–9 and a–f) and calculated based on the contents of a file or directory structure in Git.
 A SHA-1 hash looks something like this:
 
@@ -208,23 +209,23 @@ Before you start using Git, you have to make it available on your computer.
 Even if it's already installed, it's probably a good idea to update to the latest version.
 You can either install it as a package or via another installer, or download the source code and compile it yourself.
 
-==== Installing on Linux
+==== Installing on Linux(((Linux, installing)))
 
 If you want to install Git on Linux via a binary installer, you can generally do so through the basic package-management tool that comes with your distribution.
-If you’re on Fedora, you can use yum:
+If you’re on Fedora for example, you can use yum:
 
   $ yum install git
 
-Or if you’re on a Debian-based distribution like Ubuntu, try apt-get:
+If you’re on a Debian-based distribution like Ubuntu, try apt-get:
 
   $ apt-get install git
 
 For more options, there are instructions for installing on several different Unix flavors on the Git website, at http://git-scm.com/download/linux[].
 
-==== Installing on Mac
+==== Installing on Mac(((Mac, installing)))
 
 There are several ways to install Git on a Mac.
-The easiest is probably to install the Xcode Command Line Tools.
+The easiest is probably to install the Xcode Command Line Tools.(((Xcode)))
 On Mavericks (10.9) or above you can do this simply by trying to run 'git' from the Terminal the very first time.
 If you don't have it installed already, it will prompt you to install it.
 
@@ -240,37 +241,16 @@ You can download that tool from the GitHub for Mac website, at http://mac.github
 
 ==== Installing on Windows
 
-There are also a few ways to install Git on Windows.
+There are also a few ways to install Git on Windows.(((Windows, installing)))
 The most official build is available for download on the Git website.
 Just go to http://git-scm.com/download/win[] and the download will start automatically.
 Note that this is a project called Git for Windows (also called msysGit), which is separate from Git itself; for more information on it, go to http://msysgit.github.io/[].
 
-
 Another easy way to get Git installed is by installing GitHub for Windows.
 The installer includes a command line version of Git as well as the GUI.
 It also works well with Powershell, and sets up solid credential caching and sane CRLF settings.
 We'll learn more about those things a little later, but suffice it to say they're things you want.
 
-=== First-Time Git Setup
-
-Now that you have Git on your system, you’ll want to do a few things to customize your Git environment.
-You should have to do these things only once on any given computer; they’ll stick around between upgrades.
-You can also change them at any time by running through the commands again.
-
-Git comes with a tool called `git config` that lets you get and set configuration variables that control all aspects of how Git looks and operates.
-These variables can be stored in three different places:
-
-1. `/etc/gitconfig` file: Contains values for every user on the system and all their repositories.
-  If you pass the option` --system` to `git config`, it reads and writes from this file specifically.
-2. `~/.gitconfig` or `~/.config/git/config` file: Specific to your user.
-  You can make Git read and write to this file specifically by passing the `--global` option.
-3. `config` file in the Git directory (that is, `.git/config`) of whatever repository you’re currently using: Specific to that single repository.
-
-Each level overrides values in the previous level, so values in `.git/config` trump those in `/etc/gitconfig`.
-
-On Windows systems, Git looks for the `.gitconfig` file in the `$HOME` directory (`C:\Users\$USER` for most people).
-It also still looks for `/etc/gitconfig`, although it’s relative to the MSys root, which is wherever you decide to install Git on your Windows system when you run the installer.
-
 ==== Installing from Source
 
 Some people may instead find it useful to install Git from source, because you’ll get the most recent version.
@@ -302,27 +282,53 @@ After this is done, you can also get Git via Git itself for updates:
 
   $ git clone git://git.kernel.org/pub/scm/git/git.git
 
+
+=== First-Time Git Setup
+
+Now that you have Git on your system, you’ll want to do a few things to customize your Git environment.
+You should have to do these things only once on any given computer; they’ll stick around between upgrades.
+You can also change them at any time by running through the commands again.
+
+Git comes with a tool called `git config` that lets you get and set configuration variables that control all aspects of how Git looks and operates.(((git, config)))
+These variables can be stored in three different places:
+
+1. `/etc/gitconfig` file: Contains values for every user on the system and all their repositories.
+  If you pass the option` --system` to `git config`, it reads and writes from this file specifically.
+2. `~/.gitconfig` or `~/.config/git/config` file: Specific to your user.
+  You can make Git read and write to this file specifically by passing the `--global` option.
+3. `config` file in the Git directory (that is, `.git/config`) of whatever repository you’re currently using: Specific to that single repository.
+
+Each level overrides values in the previous level, so values in `.git/config` trump those in `/etc/gitconfig`.
+
+On Windows systems, Git looks for the `.gitconfig` file in the `$HOME` directory (`C:\Users\$USER` for most people).
+It also still looks for `/etc/gitconfig`, although it’s relative to the MSys root, which is wherever you decide to install Git on your Windows system when you run the installer.
+
 ==== Your Identity
 
 The first thing you should do when you install Git is to set your user name and e-mail address.
-This is important because every Git commit uses this information, and it’s immutably baked into the commits you pass around:
+This is important because every Git commit uses this information, and it’s immutably baked into the commits you start creating:
 
   $ git config --global user.name "John Doe"
   $ git config --global user.email [email protected]
 
 Again, you need to do this only once if you pass the `--global` option, because then Git will always use that information for anything you do on that system.
 If you want to override this with a different name or e-mail address for specific projects, you can run the command without the `--global` option when you’re in that project.
 
-Many of the GUI tools will help you do this when you first run them as well.
+Many of the GUI tools will help you do this when you first run them.
 
 ==== Your Editor
 
 Now that your identity is set up, you can configure the default text editor that will be used when Git needs you to type in a message.
-By default, Git uses your system’s default editor, which is generally vi or Vim.
+If not configured, Git uses your system’s default editor, which is generally Vim.
 If you want to use a different text editor, such as Emacs, you can do the following:
 
   $ git config --global core.editor emacs
 
+[NOTE]
+====
+Vim and Emacs are popular text editors often used by developers on Unix based systems like Linux and Mac. If you are not familiar with either of these editors or are on a Windows system, you may need to search for instructions for how to set up your favorite editor with Git.
+====
+
 ==== Checking Your Settings
 
 If you want to check your settings, you can use the `git config --list` command to list all the settings Git can find at that point:
@@ -339,7 +345,7 @@ If you want to check your settings, you can use the `git config --list` command
 You may see keys more than once, because Git reads the same key from different files (`/etc/gitconfig` and `~/.gitconfig`, for example).
 In this case, Git uses the last value for each unique key it sees.
 
-You can also check what Git thinks a specific key’s value is by typing `git config <key>`:
+You can also check what Git thinks a specific key’s value is by typing `git config <key>`:(((git, config)))
 
   $ git config user.name
   John Doe
@@ -352,16 +358,16 @@ If you ever need help while using Git, there are three ways to get the manual pa
   $ git <verb> --help
   $ man git-<verb>
 
-For example, you can get the manpage help for the config command by running
+For example, you can get the manpage help for the config command by running(((git, help)))
 
   $ git help config
 
 These commands are nice because you can access them anywhere, even offline.
 If the manpages and this book aren’t enough and you need in-person help, you can try the `#git` or `#github` channel on the Freenode IRC server (irc.freenode.net).
-These channels are regularly filled with hundreds of people who are all very knowledgeable about Git and are often willing to help.
+These channels are regularly filled with hundreds of people who are all very knowledgeable about Git and are often willing to help.(((IRC)))
 
 === Summary
 
-You should have a basic understanding of what Git is and how it’s different from the CVCS you may have been using.
+You should have a basic understanding of what Git is and how it’s different from the centralized version control system you may have previously been using.
 You should also now have a working version of Git on your system that’s set up with your personal identity.
 It’s now time to learn some Git basics.