From 8f76dc6fae3bb5536b36c987aa521322dcdd220c Mon Sep 17 00:00:00 2001
From: Junio C Hamano
Date: Wed, 17 Jan 2007 07:24:25 +0000
Subject: [PATCH] Autogenerated HTML docs for v1.5.0-rc1-g936f3
---
config.txt | 7 ++++++-
git-commit.html | 7 ++++++-
git-commit.txt | 6 ++++++
git-repo-config.html | 8 ++++++--
4 files changed, 24 insertions(+), 4 deletions(-)
diff --git a/config.txt b/config.txt
index faa17ba84..da7fde56b 100644
--- a/config.txt
+++ b/config.txt
@@ -2,7 +2,12 @@ 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
+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
diff --git a/git-commit.html b/git-commit.html
index efc284477..b96d40abe 100644
--- a/git-commit.html
+++ b/git-commit.html
@@ -548,6 +548,11 @@ refuses to run when given pathnames (but see -i option).
+
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.
-
@@ -651,7 +656,7 @@ Junio C Hamano <junkio@cox.net>