Autogenerated man pages for v1.5.0-rc1-g936f3

diff --git a/man1/git-commit.1 b/man1/git-commit.1
index 61e9b2c1f43034be0cb44619e90b4fec808b8117..97a4d098d28261399157ab7078b3933f9efc1d22 100644 (file)
--- a/man1/git-commit.1
+++ b/man1/git-commit.1
@@ -131,6 +131,8 @@ $ git commit
 .fi
 As with the case to record your own changes, you can use \-a option to save typing. One difference is that during a merge resolution, you cannot use git commit with pathnames to alter the order the changes are committed, because the merge should be recorded as a single commit. In fact, the command refuses to run when given pathnames (but see \-i option).
 .SH "DISCUSSION"
+Though not required, it's a good idea to begin the commit message with a single short (less than 50 character) line summarizing the change, followed by a blank line and then a more thorough description. Tools that turn commits into email, for example, use the first line on the Subject: line and the rest of the commit in the body.
+
 At the core level, git is character encoding agnostic.
 .TP 3
 \(bu

diff --git a/man1/git-repo-config.1 b/man1/git-repo-config.1
index fe3f90288a923a38c44888923dcf64482095b249..3d5810829f378bcecc1485f1e7a9994d53385e75 100644 (file)
--- a/man1/git-repo-config.1
+++ b/man1/git-repo-config.1
@@ -2,7 +2,7 @@
 .\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
 .\" Instead of manually editing it, you probably should edit the DocBook XML
 .\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-REPO\-CONFIG" "1" "01/15/2007" "" ""
+.TH "GIT\-REPO\-CONFIG" "1" "01/17/2007" "" ""
 .\" disable hyphenation
 .nh
 .\" disable justification (adjust text to left margin only)
@@ -184,7 +184,9 @@ To add a new proxy, without altering any of the existing ones, use
 % git repo\-config core.gitproxy '"proxy" for example.com'
 .fi
 .SH "CONFIGURATION FILE"
-The git configuration file contains a number of variables that affect the git command's behavior. They can be used by both the git plumbing and the porcelains. The variables are divided into sections, where in the fully qualified variable name the variable itself is the last dot\-separated segment and the section name is everything before the last dot. The variable names are case\-insensitive and only alphanumeric characters are allowed. Some variables may appear multiple times.
+The git configuration file contains a number of variables that affect the git command's behavior. .git/config file for each repository is used to store the information for that repository, and $HOME/.gitconfig is used to store per user information to give fallback values for .git/config file.
+
+They can be used by both the git plumbing and the porcelains. The variables are divided into sections, where in the fully qualified variable name the variable itself is the last dot\-separated segment and the section name is everything before the last dot. The variable names are case\-insensitive and only alphanumeric characters are allowed. Some variables may appear multiple times.
 
 The syntax is fairly flexible and permissive; whitespaces are mostly ignored. The \fI#\fR and \fI;\fR characters begin comments to the end of line, blank lines are ignored, lines containing strings enclosed in square brackets start sections and all the other lines are recognized as setting variables, in the form \fIname = value\fR. If there is no equal sign on the line, the entire line is taken as \fIname\fR and the variable is recognized as boolean "true". String values may be entirely or partially enclosed in double quotes; some variables may require special value format.
 .SS "Example"