If true, this remote will be skipped by default when updating - using the remote subcommand of git-remote(1). + using the update subcommand of git-remote(1).
Table of Contents
Git is a fast distributed revision control system.
This manual is designed to be readable by someone with basic UNIX +
Table of Contents
Git is a fast distributed revision control system.
This manual is designed to be readable by someone with basic UNIX command-line skills, but no previous knowledge of git.
Chapter 1, Repositories and Branches and Chapter 2, Exploring git history explain how to fetch and study a project using gitâread these chapters to learn how to build and test a particular version of a software project, search for @@ -23,7 +23,7 @@ of files. It stores the history as a compressed collection of interrelated snapshots of the project's contents. In git each such version is called a commit.
Those snapshots aren't necessarily all arranged in a single line from oldest to newest; instead, work may simultaneously proceed along -parallel lines of development, called <def_branch,branches>>, which may +parallel lines of development, called branches, which may merge and diverge.
A single git repository can track development on multiple branches. It does this by keeping a list of heads which reference the latest commit on each branch; the git-branch(1) command shows @@ -1449,7 +1449,7 @@ column in the git-ls-files(1) outp number, and will take on values other than 0 for files with merge conflicts.
The index is thus a sort of temporary staging area, which is filled with a tree which you are in the process of working on.
If you blow the index away entirely, you generally haven't lost any -information as long as you have the name of the tree that it described.
Table of Contents
Large projects are often composed of smaller, self-contained modules. For +information as long as you have the name of the tree that it described.
Table of Contents
Large projects are often composed of smaller, self-contained modules. For
example, an embedded Linux distribution's source tree would include every
piece of software in the distribution with some local modifications; a movie
player might need to build against a specific, known-working version of a
@@ -1543,7 +1543,7 @@ index d266b98..261dfac 160000
$ git add a
$ git commit -m "Updated submodule a."
$ git push
You have to run git submodule update after git pull if you want to update
-submodules, too.
Always publish the submodule change before publishing the change to the +submodules, too.
Always publish the submodule change before publishing the change to the superproject that references it. If you forget to publish the submodule change, others won't be able to clone the repository:
$ cd ~/git/super/a
$ echo i added another line to this file >> a.txt
diff --git a/user-manual.txt b/user-manual.txt
index f2b42068f..3f552e9d8 100644
--- a/user-manual.txt
+++ b/user-manual.txt
@@ -74,7 +74,7 @@ version is called a <