Table of Contents
Table of Contents
Git is a fast distributed revision control system.
\nThis manual is designed to be readable by someone with basic UNIX\n command-line skills, but no previous knowledge of Git.
\n-Chapter 1, Repositories \nand Branches and Chapter 2, Exploring Git history explain how\n+
Chapter 2, Repositories \nand Branches and Chapter 3, Exploring Git history explain how\n to fetch and study a project using git—read these chapters to learn how\n to build and test a particular version of a software project, search for\n regressions, and so on.
\nPeople needing to do actual development will also want to read\n-Chapter 3, Developing with Git \nand Chapter 4, Sharing development with others.
\n+Chapter 4, Developing with Git \nand Chapter 5, Sharing development with others.\nFurther chapters cover more specialized topics.
\nComprehensive reference documentation is available through the man\n pages, or git-help(1) command. For example, for the command\n@@ -26,7 +26,7 @@\n
Finally, see Appendix B, Notes and todo list for this manual for ways that you can help make this manual more\n complete.
\nTable of Contents
Table of Contents
In fact, in Chapter 7, Git concepts we shall see that everything stored in Git\n+
In fact, in Chapter 8, Git concepts we shall see that everything stored in Git\n history, including file data and directory contents, is stored in an object\n with a name that is a hash of its contents.
\nTable of Contents
Table of Contents
Git is best thought of as a tool for storing the history of a\n collection of files. It does this by storing compressed snapshots of\n@@ -679,7 +679,7 @@\n
Table of Contents
Table of Contents
It is also possible to replace commits further back in the history, but\n this is an advanced topic to be left for\n-another chapter.
\n+another chapter.\nTable of Contents
Table of Contents
Now create the branches in which you are going to work; these start out\n at the current tip of origin/master branch, and should be set up (using\n the --track option to git-branch(1)) to merge changes in from\n@@ -1679,7 +1679,7 @@\n
Table of Contents
Table of Contents
Normally commits are only added to a project, never taken away or\n replaced. Git is designed with this assumption, and violating it will\n@@ -1923,7 +1923,7 @@\n publishing.
\nTable of Contents
Table of Contents
Table of Contents
Table of Contents
Git is built on a small number of simple but powerful ideas. While it\n is possible to get things done without understanding them, you will find\n@@ -2141,7 +2141,7 @@\n between two related tree objects, since it can ignore any entries with\n identical object names.
\n(Note: in the presence of submodules, trees may also have commits as\n-entries. See Chapter 8, Submodules for documentation.)
\n+entries. See Chapter 9, Submodules for documentation.)\nNote that the files all have mode 644 or 755: Git actually only pays\n attention to the executable bit.
\nThe most common cause of dangling objects is that you’ve rebased a\n branch, or you have pulled from somebody else who rebased a branch—see\n-Chapter 5, Rewriting history and maintaining patch series. In that case, the old head of the original\n+Chapter 6, Rewriting history and maintaining patch series. In that case, the old head of the original\n branch still exists, as does everything it pointed to. The branch\n pointer itself just doesn’t, since you replaced it with another one.
\nThere are also other situations that cause dangling objects. For\n@@ -2437,7 +2437,7 @@\n information as long as you have the name of the tree that it described.
\nTable of Contents
Table of Contents
Large projects are often composed of smaller, self-contained modules. \n For\n example, an embedded Linux distribution’s source tree would include every\n@@ -2629,7 +2629,7 @@\n warning about not being able switch from a dirty branch.
\nTable of Contents
Table of Contents
Many of the higher-level commands were originally implemented as shell\n scripts using a smaller core of low-level Git commands. These can still\n@@ -2891,7 +2891,7 @@\n
and that is what higher level git merge -s resolve is implemented with.
Table of Contents
Table of Contents
This chapter covers internal details of the Git implementation which\n probably only Git developers need to understand.
\n@@ -3072,7 +3072,7 @@\n itself!\nTable of Contents
Table of Contents