Autogenerated HTML docs for v1.5.0-rc1-g936f3

diff --git a/config.txt b/config.txt
index faa17ba..da7fde5 100644 (file)
--- 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 efc2844..b96d40a 100644 (file)
--- a/git-commit.html
+++ b/git-commit.html
@@ -548,6 +548,11 @@ refuses to run when given pathnames (but see <tt>-i</tt> option).</p>
 </div>\r
 <h2>DISCUSSION</h2>\r
 <div class="sectionbody">\r
+<p>Though not required, it's a good idea to begin the commit message\r
+with a single short (less than 50 character) line summarizing the\r
+change, followed by a blank line and then a more thorough description.\r
+Tools that turn commits into email, for example, use the first line\r
+on the Subject: line and the rest of the commit in the body.</p>\r
 <p>At the core level, git is character encoding agnostic.</p>\r
 <ul>\r
 <li>\r
@@ -651,7 +656,7 @@ Junio C Hamano &lt;junkio@cox.net&gt;</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 17-Jan-2007 05:40:13 UTC\r
+Last updated 17-Jan-2007 07:24:19 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-commit.txt b/git-commit.txt
index 6139386..9c84353 100644 (file)
--- a/git-commit.txt
+++ b/git-commit.txt
@@ -218,6 +218,12 @@ refuses to run when given pathnames (but see `-i` option).
 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.
+
 include::i18n.txt[]
 
 ENVIRONMENT VARIABLES

diff --git a/git-repo-config.html b/git-repo-config.html
index 0e5a679..fcb8283 100644 (file)
--- a/git-repo-config.html
+++ b/git-repo-config.html
@@ -562,7 +562,11 @@ i.e. the one without a "for &#8230;" postfix, do something like this:</p>
 <h2>CONFIGURATION FILE</h2>\r
 <div class="sectionbody">\r
 <p>The git configuration file contains a number of variables that affect\r
-the git command's behavior. They can be used by both the git plumbing\r
+the git command's behavior. <tt>.git/config</tt> file for each repository\r
+is used to store the information for that repository, and\r
+<tt>$HOME/.gitconfig</tt> is used to store per user information to give\r
+fallback values for <tt>.git/config</tt> file.</p>\r
+<p>They can be used by both the git plumbing\r
 and the porcelains. The variables are divided into sections, where\r
 in the fully qualified variable name the variable itself is the last\r
 dot-separated segment and the section name is everything before the last\r
@@ -1280,7 +1284,7 @@ receive.denyNonFastForwards
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 15-Jan-2007 06:12:32 UTC\r
+Last updated 17-Jan-2007 07:24:20 UTC\r
 </div>\r
 </div>\r
 </body>\r