Convert the rest to new page parser code paths

And remove some now unused code.

See #5324

9 files changed, 50 insertions, 1364 deletions

diff --git a/parser/frontmatter.go b/parser/frontmatter.go
index a42db0cca..ab1bc4d55 100644
--- a/parser/frontmatter.go
+++ b/parser/frontmatter.go
@@ -13,14 +13,10 @@
 
 package parser
 
-// TODO(bep) archetype remove unused from this package.
-
 import (
-	"bytes"
 	"encoding/json"
 	"errors"
 	"io"
-	"strings"
 
 	"github.com/gohugoio/hugo/parser/metadecoders"
 
@@ -29,53 +25,12 @@ import (
 	"gopkg.in/yaml.v2"
 )
 
-// FrontmatterType represents a type of frontmatter.
-type FrontmatterType struct {
-	// Parse decodes content into a Go interface.
-	Parse func([]byte) (map[string]interface{}, error)
-
-	markstart, markend []byte // starting and ending delimiters
-	includeMark        bool   // include start and end mark in output
-}
-
-// InterfaceToConfig encodes a given input based upon the mark and writes to w.
-func InterfaceToConfig(in interface{}, mark rune, w io.Writer) error {
-	if in == nil {
-		return errors.New("input was nil")
-	}
-
-	switch mark {
-	case rune(YAMLLead[0]):
-		b, err := yaml.Marshal(in)
-		if err != nil {
-			return err
-		}
-
-		_, err = w.Write(b)
-		return err
-
-	case rune(TOMLLead[0]):
-		return toml.NewEncoder(w).Encode(in)
-	case rune(JSONLead[0]):
-		b, err := json.MarshalIndent(in, "", "   ")
-		if err != nil {
-			return err
-		}
-
-		_, err = w.Write(b)
-		if err != nil {
-			return err
-		}
-
-		_, err = w.Write([]byte{'\n'})
-		return err
-
-	default:
-		return errors.New("Unsupported Format provided")
-	}
-}
+const (
+	yamlDelimLf = "---\n"
+	tomlDelimLf = "+++\n"
+)
 
-func InterfaceToConfig2(in interface{}, format metadecoders.Format, w io.Writer) error {
+func InterfaceToConfig(in interface{}, format metadecoders.Format, w io.Writer) error {
 	if in == nil {
 		return errors.New("input was nil")
 	}
@@ -111,136 +66,42 @@ func InterfaceToConfig2(in interface{}, format metadecoders.Format, w io.Writer)
 	}
 }
 
-func InterfaceToFrontMatter2(in interface{}, format metadecoders.Format, w io.Writer) error {
+func InterfaceToFrontMatter(in interface{}, format metadecoders.Format, w io.Writer) error {
 	if in == nil {
 		return errors.New("input was nil")
 	}
 
 	switch format {
 	case metadecoders.YAML:
-		_, err := w.Write([]byte(YAMLDelimUnix))
+		_, err := w.Write([]byte(yamlDelimLf))
 		if err != nil {
 			return err
 		}
 
-		err = InterfaceToConfig2(in, format, w)
+		err = InterfaceToConfig(in, format, w)
 		if err != nil {
 			return err
 		}
 
-		_, err = w.Write([]byte(YAMLDelimUnix))
+		_, err = w.Write([]byte(yamlDelimLf))
 		return err
 
 	case metadecoders.TOML:
-		_, err := w.Write([]byte(TOMLDelimUnix))
+		_, err := w.Write([]byte(tomlDelimLf))
 		if err != nil {
 			return err
 		}
 
-		err = InterfaceToConfig2(in, format, w)
+		err = InterfaceToConfig(in, format, w)
 
 		if err != nil {
 			return err
 		}
 
-		_, err = w.Write([]byte("\n" + TOMLDelimUnix))
+		_, err = w.Write([]byte("\n" + tomlDelimLf))
 		return err
 
 	default:
-		return InterfaceToConfig2(in, format, w)
-	}
-}
-
-// InterfaceToFrontMatter encodes a given input into a frontmatter
-// representation based upon the mark with the appropriate front matter delimiters
-// surrounding the output, which is written to w.
-func InterfaceToFrontMatter(in interface{}, mark rune, w io.Writer) error {
-	if in == nil {
-		return errors.New("input was nil")
+		return InterfaceToConfig(in, format, w)
 	}
-
-	switch mark {
-	case rune(YAMLLead[0]):
-		_, err := w.Write([]byte(YAMLDelimUnix))
-		if err != nil {
-			return err
-		}
-
-		err = InterfaceToConfig(in, mark, w)
-		if err != nil {
-			return err
-		}
-
-		_, err = w.Write([]byte(YAMLDelimUnix))
-		return err
-
-	case rune(TOMLLead[0]):
-		_, err := w.Write([]byte(TOMLDelimUnix))
-		if err != nil {
-			return err
-		}
-
-		err = InterfaceToConfig(in, mark, w)
-
-		if err != nil {
-			return err
-		}
-
-		_, err = w.Write([]byte("\n" + TOMLDelimUnix))
-		return err
-
-	default:
-		return InterfaceToConfig(in, mark, w)
-	}
-}
-
-// FormatToLeadRune takes a given format kind and return the leading front
-// matter delimiter.
-func FormatToLeadRune(kind string) rune {
-	switch FormatSanitize(kind) {
-	case "yaml":
-		return rune([]byte(YAMLLead)[0])
-	case "json":
-		return rune([]byte(JSONLead)[0])
-	case "org":
-		return '#'
-	default:
-		return rune([]byte(TOMLLead)[0])
-	}
-}
-
-// FormatSanitize returns the canonical format name for a given kind.
-//
-// TODO(bep) move to helpers
-func FormatSanitize(kind string) string {
-	switch strings.ToLower(kind) {
-	case "yaml", "yml":
-		return "yaml"
-	case "toml", "tml":
-		return "toml"
-	case "json", "js":
-		return "json"
-	case "org":
-		return kind
-	default:
-		return "toml"
-	}
-}
-
-// removeTOMLIdentifier removes, if necessary, beginning and ending TOML
-// frontmatter delimiters from a byte slice.
-func removeTOMLIdentifier(datum []byte) []byte {
-	ld := len(datum)
-	if ld < 8 {
-		return datum
-	}
-
-	b := bytes.TrimPrefix(datum, []byte(TOMLDelim))
-	if ld-len(b) != 3 {
-		// No TOML prefix trimmed, so bail out
-		return datum
-	}
-
-	b = bytes.Trim(b, "\r\n")
-	return bytes.TrimSuffix(b, []byte(TOMLDelim))
 }
diff --git a/parser/frontmatter_test.go b/parser/frontmatter_test.go
index d6e6e79c3..9d9b7c3b8 100644
--- a/parser/frontmatter_test.go
+++ b/parser/frontmatter_test.go
@@ -15,55 +15,55 @@ package parser
 
 import (
 	"bytes"
-	"fmt"
 	"reflect"
-	"strings"
 	"testing"
+
+	"github.com/gohugoio/hugo/parser/metadecoders"
 )
 
 func TestInterfaceToConfig(t *testing.T) {
 	cases := []struct {
-		input interface{}
-		mark  byte
-		want  []byte
-		isErr bool
+		input  interface{}
+		format metadecoders.Format
+		want   []byte
+		isErr  bool
 	}{
 		// TOML
-		{map[string]interface{}{}, TOMLLead[0], nil, false},
+		{map[string]interface{}{}, metadecoders.TOML, nil, false},
 		{
 			map[string]interface{}{"title": "test 1"},
-			TOMLLead[0],
+			metadecoders.TOML,
 			[]byte("title = \"test 1\"\n"),
 			false,
 		},
 
 		// YAML
-		{map[string]interface{}{}, YAMLLead[0], []byte("{}\n"), false},
+		{map[string]interface{}{}, metadecoders.YAML, []byte("{}\n"), false},
 		{
 			map[string]interface{}{"title": "test 1"},
-			YAMLLead[0],
+			metadecoders.YAML,
 			[]byte("title: test 1\n"),
 			false,
 		},
 
 		// JSON
-		{map[string]interface{}{}, JSONLead[0], []byte("{}\n"), false},
+		{map[string]interface{}{}, metadecoders.JSON, []byte("{}\n"), false},
 		{
 			map[string]interface{}{"title": "test 1"},
-			JSONLead[0],
+			metadecoders.JSON,
 			[]byte("{\n   \"title\": \"test 1\"\n}\n"),
 			false,
 		},
 
 		// Errors
-		{nil, TOMLLead[0], nil, true},
-		{map[string]interface{}{}, '$', nil, true},
+		{nil, metadecoders.TOML, nil, true},
+		{map[string]interface{}{}, "foo", nil, true},
 	}
 
 	for i, c := range cases {
 		var buf bytes.Buffer
 
-		err := InterfaceToConfig(c.input, rune(c.mark), &buf)
+		err := InterfaceToConfig(c.input, c.format, &buf)
 		if err != nil {
 			if c.isErr {
 				continue
@@ -76,179 +76,3 @@ func TestInterfaceToConfig(t *testing.T) {
 		}
 	}
 }
-
-func TestInterfaceToFrontMatter(t *testing.T) {
-	cases := []struct {
-		input interface{}
-		mark  rune
-		want  []byte
-		isErr bool
-	}{
-		// TOML
-		{map[string]interface{}{}, '+', []byte("+++\n\n+++\n"), false},
-		{
-			map[string]interface{}{"title": "test 1"},
-			'+',
-			[]byte("+++\ntitle = \"test 1\"\n\n+++\n"),
-			false,
-		},
-
-		// YAML
-		{map[string]interface{}{}, '-', []byte("---\n{}\n---\n"), false}, //
-		{
-			map[string]interface{}{"title": "test 1"},
-			'-',
-			[]byte("---\ntitle: test 1\n---\n"),
-			false,
-		},
-
-		// JSON
-		{map[string]interface{}{}, '{', []byte("{}\n"), false},
-		{
-			map[string]interface{}{"title": "test 1"},
-			'{',
-			[]byte("{\n   \"title\": \"test 1\"\n}\n"),
-			false,
-		},
-
-		// Errors
-		{nil, '+', nil, true},
-		{map[string]interface{}{}, '$', nil, true},
-	}
-
-	for i, c := range cases {
-		var buf bytes.Buffer
-		err := InterfaceToFrontMatter(c.input, c.mark, &buf)
-		if err != nil {
-			if c.isErr {
-				continue
-			}
-			t.Fatalf("[%d] unexpected error value: %v", i, err)
-		}
-
-		if !reflect.DeepEqual(buf.Bytes(), c.want) {
-			t.Errorf("[%d] not equal:\nwant %q,\n got %q", i, c.want, buf.Bytes())
-		}
-	}
-}
-
-func TestFormatToLeadRune(t *testing.T) {
-	for i, this := range []struct {
-		kind   string
-		expect rune
-	}{
-		{"yaml", '-'},
-		{"yml", '-'},
-		{"toml", '+'},
-		{"tml", '+'},
-		{"json", '{'},
-		{"js", '{'},
-		{"org", '#'},
-		{"unknown", '+'},
-	} {
-		result := FormatToLeadRune(this.kind)
-
-		if result != this.expect {
-			t.Errorf("[%d] got %q but expected %q", i, result, this.expect)
-		}
-	}
-}
-
-func TestRemoveTOMLIdentifier(t *testing.T) {
-	cases := []struct {
-		input string
-		want  string
-	}{
-		{"a = 1", "a = 1"},
-		{"a = 1\r\n", "a = 1\r\n"},
-		{"+++\r\na = 1\r\n+++\r\n", "a = 1\r\n"},
-		{"+++\na = 1\n+++\n", "a = 1\n"},
-		{"+++\nb = \"+++ oops +++\"\n+++\n", "b = \"+++ oops +++\"\n"},
-		{"+++\nc = \"\"\"+++\noops\n+++\n\"\"\"\"\n+++\n", "c = \"\"\"+++\noops\n+++\n\"\"\"\"\n"},
-		{"+++\nd = 1\n+++", "d = 1\n"},
-	}
-
-	for i, c := range cases {
-		res := removeTOMLIdentifier([]byte(c.input))
-		if string(res) != c.want {
-			t.Errorf("[%d] given %q\nwant: %q\n got: %q", i, c.input, c.want, res)
-		}
-	}
-}
-
-func BenchmarkFrontmatterTags(b *testing.B) {
-
-	for _, frontmatter := range []string{"JSON", "YAML", "YAML2", "TOML"} {
-		for i := 1; i < 60; i += 20 {
-			doBenchmarkFrontmatter(b, frontmatter, i)
-		}
-	}
-}
-
-func doBenchmarkFrontmatter(b *testing.B, fileformat string, numTags int) {
-	yamlTemplate := `---
-name: "Tags"
-tags:
-%s
----
-`
-
-	yaml2Template := `---
-name: "Tags"
-tags: %s
----
-`
-	tomlTemplate := `+++
-name = "Tags"
-tags = %s
-+++
-`
-
-	jsonTemplate := `{
-	"name": "Tags",
-	"tags": [
-		%s
-	]
-}`
-	name := fmt.Sprintf("%s:%d", fileformat, numTags)
-	b.Run(name, func(b *testing.B) {
-		tags := make([]string, numTags)
-		var (
-			tagsStr             string
-			frontmatterTemplate string
-		)
-		for i := 0; i < numTags; i++ {
-			tags[i] = fmt.Sprintf("Hugo %d", i+1)
-		}
-		if fileformat == "TOML" {
-			frontmatterTemplate = tomlTemplate
-			tagsStr = strings.Replace(fmt.Sprintf("%q", tags), " ", ", ", -1)
-		} else if fileformat == "JSON" {
-			frontmatterTemplate = jsonTemplate
-			tagsStr = strings.Replace(fmt.Sprintf("%q", tags), " ", ", ", -1)
-		} else if fileformat == "YAML2" {
-			frontmatterTemplate = yaml2Template
-			tagsStr = strings.Replace(fmt.Sprintf("%q", tags), " ", ", ", -1)
-		} else {
-			frontmatterTemplate = yamlTemplate
-			for _, tag := range tags {
-				tagsStr += "\n- " + tag
-			}
-		}
-
-		frontmatter := fmt.Sprintf(frontmatterTemplate, tagsStr)
-
-		p := page{frontmatter: []byte(frontmatter)}
-
-		b.ResetTimer()
-		for i := 0; i < b.N; i++ {
-			meta, err := p.Metadata()
-			if err != nil {
-				b.Fatal(err)
-			}
-			if meta == nil {
-				b.Fatal("Meta is nil")
-			}
-		}
-	})
-}
diff --git a/parser/long_text_test.md b/parser/long_text_test.md
deleted file mode 100644
index e0cac502c..000000000
--- a/parser/long_text_test.md
+++ /dev/null
@@ -1,263 +0,0 @@
----
-title: The Git Book - Long Text
----
-# Getting Started #
-
-This chapter will be about getting started with Git.  We will begin at the beginning by explaining some background on version control tools, then move on to how to get Git running on your system and finally how to get it setup to start working with.  At the end of this chapter you should understand why Git is around, why you should use it and you should be all setup to do so.
-
-## About Version Control ##
-
-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. Even though the examples in this book show software source code as the files under version control, in reality any type of file on a computer can be placed under version control.
-
-If you are a graphic or web designer and want to keep every version of an image or layout (which you certainly would), it is very wise to use a Version Control System (VCS). A VCS allows you to: revert files back to a previous state, revert the entire project back to a previous state, review changes made over time, see who last modified something that might be causing a problem, who introduced an issue and when, and more. Using a VCS also means that if you screw things up or lose files, you can generally recover easily. In addition, you get all this for very little overhead.
-
-### Local Version Control Systems ###
-
-Many people’s version-control method of choice is to copy files into another directory (perhaps a time-stamped directory, if they’re clever). This approach is very common because it is so simple, but it is also incredibly error prone. It is easy to forget which directory you’re in and accidentally write to the wrong file or copy over files you don’t mean to.
-
-To deal with this issue, programmers long ago developed local VCSs that had a simple database that kept all the changes to files under revision control (see Figure 1-1).
-
-Insert 18333fig0101.png
-Figure 1-1. Local version control diagram.
-
-One of the more popular VCS tools was a system called rcs, which is still distributed with many computers today. Even the popular Mac OS X operating system includes the rcs command when you install the Developer Tools. This tool basically works by keeping patch sets (that is, the differences between files) from one revision to another in a special format on disk; it can then recreate what any file looked like at any point in time by adding up all the patches.
-
-### Centralized Version Control Systems ###
-
-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. For many years, this has been the standard for version control (see Figure 1-2).
-
-Insert 18333fig0102.png
-Figure 1-2. Centralized version control diagram.
-
-This setup offers many advantages, especially over local VCSs. For example, everyone knows to a certain degree what everyone else on the project is doing. Administrators have fine-grained control over who can do what; and it’s far easier to administer a CVCS than it is to deal with local databases on every client.
-
-However, this setup also has some serious downsides. The most obvious is the single point of failure that the centralized server represents. If that server goes down for an hour, then during that hour nobody can collaborate at all or save versioned changes to anything they’re working on. If the hard disk the central database is on becomes corrupted, and proper backups haven’t been kept, you lose absolutely everything—the entire history of the project except whatever single snapshots people happen to have on their local machines. Local VCS systems suffer from this same problem—whenever you have the entire history of the project in a single place, you risk losing everything.
-
-### Distributed Version Control Systems ###
-
-This is where Distributed Version Control Systems (DVCSs) step in. In a DVCS (such as Git, Mercurial, Bazaar or Darcs), clients don’t just check out the latest snapshot of the files: they fully mirror the repository. Thus if any server dies, and these systems were collaborating via it, any of the client repositories can be copied back up to the server to restore it. Every checkout is really a full backup of all the data (see Figure 1-3).
-
-Insert 18333fig0103.png
-Figure 1-3. Distributed version control diagram.
-
-Furthermore, many of these systems deal pretty well with having several remote repositories they can work with, so you can collaborate with different groups of people in different ways simultaneously within the same project. This allows you to set up several types of workflows that aren’t possible in centralized systems, such as hierarchical models.
-
-## A Short History of Git ##
-
-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. 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 system called 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. 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)
-
-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 Chapter 3).
-
-## Git Basics ##
-
-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; understanding those differences will help prevent you from becoming confused while using it.
-
-### Snapshots, Not Differences ###
-
-The major difference between Git and any other VCS (Subversion and friends included) is the way Git thinks about its data. Conceptually, most other systems store information as a list of file-based changes. These systems (CVS, Subversion, Perforce, Bazaar, and so on) think of the information they keep as a set of files and the changes made to each file over time, as illustrated in Figure 1-4.
-
-Insert 18333fig0104.png
-Figure 1-4. Other systems tend to store data as changes to a base version of each file.
-
-Git doesn’t think of or store its data this way. Instead, Git thinks of its data more like a set of snapshots of a mini filesystem. Every time you commit, or save the state of your project in Git, it basically takes a picture of what all your files look like at that moment and stores a reference to that snapshot. To be efficient, if files have not changed, Git doesn’t store the file again—just a link to the previous identical file it has already stored. Git thinks about its data more like Figure 1-5.
-
-Insert 18333fig0105.png
-Figure 1-5. Git stores data as snapshots of the project over time.
-
-This is an important distinction between Git and nearly all other VCSs. It makes Git reconsider almost every aspect of version control that most other systems copied from the previous generation. This makes Git more like a mini filesystem with some incredibly powerful tools built on top of it, rather than simply a VCS. We’ll explore some of the benefits you gain by thinking of your data this way when we cover Git branching in Chapter 3.
-
-### Nearly Every Operation Is Local ###
-
-Most operations in Git only need local files and resources to operate — generally no information is needed from another computer on your network.  If you’re used to a CVCS where most operations have that network latency overhead, this aspect of Git will make you think that the gods of speed have blessed Git with unworldly powers. Because you have the entire history of the project right there on your local disk, most operations seem almost instantaneous.
-
-For example, to browse the history of the project, Git doesn’t need to go out to the server to get the history and display it for you—it simply reads it directly from your local database. This means you see the project history almost instantly. If you want to see the changes introduced between the current version of a file and the file a month ago, Git can look up the file a month ago and do a local difference calculation, instead of having to either ask a remote server to do it or pull an older version of the file from the remote server to do it locally.
-
-This also means that there is very little you can’t do if you’re offline or off VPN. If you get on an airplane or a train and want to do a little work, you can commit happily until you get to a network connection to upload. If you go home and can’t get your VPN client working properly, you can still work. In many other systems, doing so is either impossible or painful. In Perforce, for example, you can’t do much when you aren’t connected to the server; and in Subversion and CVS, you can edit files, but you can’t commit changes to your database (because your database is offline). This may not seem like a huge deal, but you may be surprised what a big difference it can make.
-
-### Git Has Integrity ###
-
-Everything in Git is check-summed before it is stored and is then referred to by that checksum. This means it’s impossible to change the contents of any file or directory without Git knowing about it. 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. 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:
-
-	24b9da6552252987aa493b52f8696cd6d3b00373
-
-You will see these hash values all over the place in Git because it uses them so much. In fact, Git stores everything not by file name but in the Git database addressable by the hash value of its contents.
-
-### Git Generally Only Adds Data ###
-
-When you do actions in Git, nearly all of them only add data to the Git database. It is very difficult to get the system to do anything that is not undoable or to make it erase data in any way. As in any VCS, you can lose or mess up changes you haven’t committed yet; but after you commit a snapshot into Git, it is very difficult to lose, especially if you regularly push your database to another repository.
-
-This makes using Git a joy because we know we can experiment without the danger of severely screwing things up. For a more in-depth look at how Git stores its data and how you can recover data that seems lost, see Chapter 9.
-
-### The Three States ###
-
-Now, pay attention. This is the main thing to remember about Git if you want the rest of your learning process to go smoothly. Git has three main states that your files can reside in: committed, modified, and staged. Committed means that the data is safely stored in your local database. Modified means that you have changed the file but have not committed it to your database yet. Staged means that you have marked a modified file in its current version to go into your next commit snapshot.
-
-This leads us to the three main sections of a Git project: the Git directory, the working directory, and the staging area.
-
-Insert 18333fig0106.png
-Figure 1-6. Working directory, staging area, and git directory.
-
-The Git directory is where Git stores the metadata and object database for your project. This is the most important part of Git, and it is what is copied when you clone a repository from another computer.
-
-The working directory is a single checkout of one version of the project. These files are pulled out of the compressed database in the Git directory and placed on disk for you to use or modify.
-
-The staging area is a simple file, generally contained in your Git directory, that stores information about what will go into your next commit. It’s sometimes referred to as the index, but it’s becoming standard to refer to it as the staging area.
-
-The basic Git workflow goes something like this:
-
-1. You modify files in your working directory.
-2. You stage the files, adding snapshots of them to your staging area.
-3. You do a commit, which takes the files as they are in the staging area and stores that snapshot permanently to your Git directory.
-
-If a particular version of a file is in the git directory, it’s considered committed. If it’s modified but has been added to the staging area, it is staged. And if it was changed since it was checked out but has not been staged, it is modified. In Chapter 2, you’ll learn more about these states and how you can either take advantage of them or skip the staged part entirely.
-
-## Installing Git ##
-
-Let’s get into using some Git. First things first—you have to install it. You can get it a number of ways; the two major ones are to install it from source or to install an existing package for your platform.
-
-### Installing from Source ###
-
-If you can, it’s generally useful to install Git from source, because you’ll get the most recent version. Each version of Git tends to include useful UI enhancements, so getting the latest version is often the best route if you feel comfortable compiling software from source. It is also the case that many Linux distributions contain very old packages; so unless you’re on a very up-to-date distro or are using backports, installing from source may be the best bet.
-
-To install Git, you need to have the following libraries that Git depends on: curl, zlib, openssl, expat, and libiconv. For example, if you’re on a system that has yum (such as Fedora) or apt-get (such as a Debian based system), you can use one of these commands to install all of the dependencies:
-
-	$ yum install curl-devel expat-devel gettext-devel \
-	  openssl-devel zlib-devel
-
-	$ apt-get install libcurl4-gnutls-dev libexpat1-dev gettext \
-	  libz-dev libssl-dev
-
-When you have all the necessary dependencies, you can go ahead and grab the latest snapshot from the Git web site:
-
-	http://git-scm.com/download
-
-Then, compile and install:
-
-	$ tar -zxf git-1.7.2.2.tar.gz
-	$ cd git-1.7.2.2
-	$ make prefix=/usr/local all
-	$ sudo make prefix=/usr/local install
-
-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
-
-### Installing on Linux ###
-
-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:
-
-	$ yum install git-core
-
-Or if you’re on a Debian-based distribution like Ubuntu, try apt-get:
-
-	$ apt-get install git
-
-### Installing on Mac ###
-
-There are two easy ways to install Git on a Mac. The easiest is to use the graphical Git installer, which you can download from the Google Code page (see Figure 1-7):
-
-	http://code.google.com/p/git-osx-installer
-
-Insert 18333fig0107.png
-Figure 1-7. Git OS X installer.
-
-The other major way is to install Git via MacPorts (`http://www.macports.org`). If you have MacPorts installed, install Git via
-
-	$ sudo port install git-core +svn +doc +bash_completion +gitweb
-
-You don’t have to add all the extras, but you’ll probably want to include +svn in case you ever have to use Git with Subversion repositories (see Chapter 8).
-
-### Installing on Windows ###
-
-Installing Git on Windows is very easy. The msysGit project has one of the easier installation procedures. Simply download the installer exe file from the GitHub page, and run it:
-
-	http://msysgit.github.com/
-
-After it’s installed, you have both a command-line version (including an SSH client that will come in handy later) and the standard GUI.
-
-Note on Windows usage: you should use Git with the provided msysGit shell (Unix style), it allows to use the complex lines of command given in this book. If you need, for some reason, to use the native Windows shell / command line console, you have to use double quotes instead of simple quotes (for parameters with spaces in them) and you must quote the parameters ending with the circumflex accent (^) if they are last on the line, as it is a continuation symbol in Windows.
-
-## 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; 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:
-
-*	`/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.
-*	`~/.gitconfig` file: Specific to your user. You can make Git read and write to this file specifically by passing the `--global` option.
-*	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 (`%USERPROFILE%` in Windows’ environment), which is `C:\Documents and Settings\$USER` or `C:\Users\$USER` for most people, depending on version (`$USER` is `%USERNAME%` in Windows’ environment). 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 a