Autogenerated man pages for v1.4.0-rc1-g99b41

diff --git a/man1/git-cvsserver.1 b/man1/git-cvsserver.1
index e5ab988ff56c8585a1733e16aa634709fb073033..dbb281898fa53b70b841a83d82caa8e836861bf5 100755 (executable)
--- a/man1/git-cvsserver.1
+++ b/man1/git-cvsserver.1
@@ -52,56 +52,43 @@ CVS clients cannot tag, branch or perform GIT merges\&.
 1.
 If you are going to offer anonymous CVS access via pserver, add a line in /etc/inetd\&.conf like
 
-.nf
-cvspserver stream tcp nowait nobody git\-cvsserver pserver
-.fi
 
 .nf
-Note: In some cases, you need to pass the 'pserver' argument twice for
-git\-cvsserver to see it\&. So the line would look like
-.fi
+   cvspserver stream tcp nowait nobody git\-cvsserver pserver
 
-.nf
-cvspserver stream tcp nowait nobody git\-cvsserver pserver pserver
 .fi
+Note: In some cases, you need to pass the \fIpserver\fR argument twice for git\-cvsserver to see it\&. So the line would look like
+
 
 .nf
-No special setup is needed for SSH access, other than having GIT tools
-in the PATH\&. If you have clients that do not accept the CVS_SERVER
-env variable, you can rename git\-cvsserver to cvs\&.
+   cvspserver stream tcp nowait nobody git\-cvsserver pserver pserver
+
 .fi
+No special setup is needed for SSH access, other than having GIT tools in the PATH\&. If you have clients that do not accept the CVS_SERVER env variable, you can rename git\-cvsserver to cvs\&.
 .TP
 2.
 For each repo that you want accessible from CVS you need to edit config in the repo and add the following section\&.
 
-.nf
-[gitcvs]
-     enabled=1
-     # optional for debugging
-     logfile=/path/to/logfile
-.fi
 
 .nf
-Note: you need to ensure each user that is going to invoke git\-cvsserver has
-write access to the log file and to the git repository\&. When offering anon
-access via pserver, this means that the nobody user should have write access
-to at least the sqlite database at the root of the repository\&.
+   [gitcvs]
+        enabled=1
+        # optional for debugging
+        logfile=/path/to/logfile
+
 .fi
+Note: you need to ensure each user that is going to invoke git\-cvsserver has write access to the log file and to the git repository\&. When offering anon access via pserver, this means that the nobody user should have write access to at least the sqlite database at the root of the repository\&.
 .TP
 3.
 On the client machine you need to set the following variables\&. CVSROOT should be set as per normal, but the directory should point at the appropriate git repo\&. For example:
 
-.nf
 For SSH access, CVS_SERVER should be set to git\-cvsserver
-.fi
 
-.nf
 Example:
-.fi
 
 .nf
-export CVSROOT=:ext:user@server:/var/git/project\&.git
-export CVS_SERVER=git\-cvsserver
+     export CVSROOT=:ext:user@server:/var/git/project\&.git
+     export CVS_SERVER=git\-cvsserver
 .fi
 .TP
 4.
@@ -111,7 +98,7 @@ For SSH clients that will make commits, make sure their \&.bashrc file sets the
 Clients should now be able to check out the project\&. Use the CVS \fImodule\fR name to indicate what GIT \fIhead\fR you want to check out\&. Example:
 
 .nf
-cvs co \-d project\-master master
+     cvs co \-d project\-master master
 .fi
 .LP
 

diff --git a/man1/git-ls-tree.1 b/man1/git-ls-tree.1
index 3ba2293c502f033d8a4783359b760e528a6e36fb..85921f9531d1d3d18e32f400453f91f56b84691c 100755 (executable)
--- a/man1/git-ls-tree.1
+++ b/man1/git-ls-tree.1
@@ -65,7 +65,7 @@ Instead of showing the full 40\-byte hexadecimal object lines, show only handful
 
 .TP
 \-\-full\-name
-Instead of showing the path names relative the current working directory, show the full path names\&.
+Instead of showing the path names relative to the current working directory, show the full path names\&.
 
 .TP
 paths

diff --git a/man1/git-repo-config.1 b/man1/git-repo-config.1
index c8c219d7a2d3a11814d8f5217954a05ca9f89875..09dc23591fd8dc1fc583cb748e7cf7f82b58ce4f 100755 (executable)
--- a/man1/git-repo-config.1
+++ b/man1/git-repo-config.1
@@ -211,10 +211,10 @@ To actually match only values with an exclamation mark, you have to
 .SH "CONFIGURATION FILE"
 
 
-The git configuration file contains a number of variables that affect the git commands behavior\&. They can be used by both the git plumbing and the porcelains\&. The variables are divided to 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\&. 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 commends 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\&.
+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"
 
@@ -235,7 +235,7 @@ The syntax is fairly flexible and permissive; whitespaces are mostly ignored\&.
 .SS "Variables"
 
 
-Note that this list is non\-comprehensive and not necessarily complete\&. For command\-specific variables, you will find more detailed description in the appropriate manual page\&. You will find description of non\-core porcelain configuration variables in the respective porcelain documentation\&.
+Note that this list is non\-comprehensive and not necessarily complete\&. For command\-specific variables, you will find a more detailed description in the appropriate manual page\&. You will find a description of non\-core porcelain configuration variables in the respective porcelain documentation\&.
 
 .TP
 core\&.fileMode
@@ -245,11 +245,7 @@ If false, the executable bit differences between the index and the working copy
 core\&.gitProxy
 A "proxy command" to execute (as \fIcommand host port\fR) instead of establishing direct connection to the remote server when using the git protocol for fetching\&. If the variable value is in the "COMMAND for DOMAIN" format, the command is applied only on hostnames ending with the specified domain string\&. This variable may be set multiple times and is matched in the given order; the first match wins\&.
 
-.nf
-Can be overridden by the 'GIT_PROXY_COMMAND' environment variable
-(which always applies universally, without the special "for"
-handling)\&.
-.fi
+Can be overridden by the \fIGIT_PROXY_COMMAND\fR environment variable (which always applies universally, without the special "for" handling)\&.
 
 .TP
 core\&.ignoreStat
@@ -277,7 +273,7 @@ If true, git will warn you if the ref name you passed it is ambiguous and might
 
 .TP
 alias\&.*
-Command aliases for the \fBgit\fR(1) command wrapper \- e\&.g\&. after defining "alias\&.last = cat\-file commit HEAD", the invocation "git last" is equivalent to "git cat\-file commit HEAD"\&. To avoid confusion, aliases that hide existing git commands are ignored\&. Arguments are split at whitespaces, but single or double quote pair can be used to quote them\&.
+Command aliases for the \fBgit\fR(1) command wrapper \- e\&.g\&. after defining "alias\&.last = cat\-file commit HEAD", the invocation "git last" is equivalent to "git cat\-file commit HEAD"\&. To avoid confusion and troubles with script usage, aliases that hide existing git commands are ignored\&. Arguments are split by spaces, the usual shell quoting and escaping is supported\&. quote pair and a backslash can be used to quote them\&.
 
 .TP
 apply\&.whitespace