From 535c26518c90b2a2d242e60c28f84a9acc8f51e5 Mon Sep 17 00:00:00 2001 From: Carl Worth Date: Fri, 28 Sep 2007 01:13:52 -0700 Subject: [PATCH] Remove trailing whitespace --- tour.mdwn | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/tour.mdwn b/tour.mdwn index ac69352..f5f4b85 100644 --- a/tour.mdwn +++ b/tour.mdwn @@ -1,4 +1,4 @@ -## Chapter 2 +## Chapter 2 A tour of git: the basics ### 2.0 Copyright @@ -50,23 +50,23 @@ install git with a single click. The package name to look for is often git, but is sometimes git-core, (due to an unfortunate name with git, meaning GNU Interactive Tools). - * Debian + * Debian apt-get install git-core - * Fedora Core + * Fedora Core yum install git - * Gentoo + * Gentoo emerge git - * OpenSUSE + * OpenSUSE yum install git - * Ubuntu + * Ubuntu apt-get install git @@ -100,7 +100,7 @@ more friendly to new users than versions 1.4 and older. If you aren't yet running version 1.5 or newer, it's highly recommended that you upgrade. - $ git version + $ git version git version 1.5.3.2 #### 2.2.1 Built-in help @@ -257,7 +257,7 @@ By default, this command prints a brief paragraph of output for each change to the project that was recorded. In git terminology, we call each of these recorded events a commit. -The fields in a record of output from “git log” are as follows. +The fields in a record of output from “git log” are as follows. * commit This field consists of a string of 40 hexadecimal characters. This is a unique identifier for referring to particular commits. @@ -286,7 +286,7 @@ several times in this chapter and the chapter that follows. * * * -![PIC][9] +![PIC][9] Figure 2.1: Graphical history of the hello repository @@ -564,7 +564,7 @@ scripted example this way. Since you’re not under the same constraint, you probably won’t want to use sed; simply use your preferred text editor to do the same thing.) - $ sed -i '/printf/a\\tprintf("hello again!\\n");' hello.c + $ sed -i '/printf/a\\tprintf("hello again!\\n");' hello.c The “git status” command will tell us what git knows about the files in the repository. @@ -683,7 +683,7 @@ the files directly. Use your favorite editor to create a file called then it will be there already). The initial contents of your .gitconfig should look like this. - # This is a git configuration file. + # This is a git configuration file. [user] name = Your Name email = you@example.com @@ -934,7 +934,7 @@ command is coneptually the combination of two commands, "git fetch" and "git merge"; we can run those separately to examine the changes before applying them locally. First we do the fetch: - $ cd hello-pull + $ cd hello-pull $ git fetch ../my-hello remote: Generating pack... Unpacking 3 objects... @@ -1105,7 +1105,7 @@ limited to working with local repositories. Each works in exactly the same fashion over a network connection; simply pass in a URL or an ssh host:/path/name specification instead of a local path. -## Appendix D +## Appendix D Open Publication License Version 1.0, 8 June 1999 -- 2.43.0