the working copy are ignored; useful on broken filesystems like FAT.
See gitlink:git-update-index[1]. True by default.
+core.autocrlf::
+ If true, makes git convert `CRLF` at the end of lines in text files to
+ `LF` when reading from the filesystem, and convert in reverse when
+ writing to the filesystem. The variable can be set to
+ 'input', in which case the conversion happens only while
+ reading from the filesystem but files are written out with
+ `LF` at the end of lines. Currently, which paths to consider
+ "text" (i.e. be subjected to the autocrlf mechanism) is
+ decided purely based on the contents.
+
core.symlinks::
If false, symbolic links are checked out as small plain files that
contain the link text. gitlink:git-update-index[1] and
The default is 15 days. See gitlink:git-rerere[1].
gitcvs.enabled::
- Whether the cvs pserver interface is enabled for this repository.
+ Whether the cvs server interface is enabled for this repository.
See gitlink:git-cvsserver[1].
gitcvs.logfile::
- Path to a log file where the cvs pserver interface well... logs
+ Path to a log file where the cvs server interface well... logs
various stuff. See gitlink:git-cvsserver[1].
+gitcvs.allbinary::
+ If true, all files are sent to the client in mode '-kb'. This
+ causes the client to treat all files as binary files which suppresses
+ any newline munging it otherwise might do. A work-around for the
+ fact that there is no way yet to set single files to mode '-kb'.
+ See gitlink:git-cvsserver[1].
+
http.sslVerify::
Whether to verify the SSL certificate when fetching or pushing
over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment
http.noEPSV::
A boolean which disables using of EPSV ftp command by curl.
- This can helpful with some "poor" ftp servers which doesn't
+ This can helpful with some "poor" ftp servers which don't
support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'
environment variable. Default is false (curl will use EPSV).
</p>\r
</dd>\r
<dt>\r
+core.autocrlf\r
+</dt>\r
+<dd>\r
+<p>\r
+ If true, makes git convert <tt>CRLF</tt> at the end of lines in text files to\r
+ <tt>LF</tt> when reading from the filesystem, and convert in reverse when\r
+ writing to the filesystem. The variable can be set to\r
+ <em>input</em>, in which case the conversion happens only while\r
+ reading from the filesystem but files are written out with\r
+ <tt>LF</tt> at the end of lines. Currently, which paths to consider\r
+ "text" (i.e. be subjected to the autocrlf mechanism) is\r
+ decided purely based on the contents.\r
+</p>\r
+</dd>\r
+<dt>\r
core.symlinks\r
</dt>\r
<dd>\r
</dt>\r
<dd>\r
<p>\r
- Whether the cvs pserver interface is enabled for this repository.\r
+ Whether the cvs server interface is enabled for this repository.\r
See <a href="git-cvsserver.html">git-cvsserver(1)</a>.\r
</p>\r
</dd>\r
</dt>\r
<dd>\r
<p>\r
- Path to a log file where the cvs pserver interface well… logs\r
+ Path to a log file where the cvs server interface well… logs\r
various stuff. See <a href="git-cvsserver.html">git-cvsserver(1)</a>.\r
</p>\r
</dd>\r
<dt>\r
+gitcvs.allbinary\r
+</dt>\r
+<dd>\r
+<p>\r
+ If true, all files are sent to the client in mode <em>-kb</em>. This\r
+ causes the client to treat all files as binary files which suppresses\r
+ any newline munging it otherwise might do. A work-around for the\r
+ fact that there is no way yet to set single files to mode <em>-kb</em>.\r
+ See <a href="git-cvsserver.html">git-cvsserver(1)</a>.\r
+</p>\r
+</dd>\r
+<dt>\r
http.sslVerify\r
</dt>\r
<dd>\r
<dd>\r
<p>\r
A boolean which disables using of EPSV ftp command by curl.\r
- This can helpful with some "poor" ftp servers which doesn't\r
+ This can helpful with some "poor" ftp servers which don't\r
support EPSV mode. Can be overridden by the <em>GIT_CURL_FTP_NO_EPSV</em>\r
environment variable. Default is false (curl will use EPSV).\r
</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 04-Apr-2007 18:33:34 UTC\r
+Last updated 14-Apr-2007 16:21:44 UTC\r
</div>\r
</div>\r
</body>\r
</li>\r
<li>\r
<p>\r
+<em>%m</em>: left, right or boundary mark\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
<em>%n</em>: newline\r
</p>\r
<dl>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 04-Apr-2007 18:33:39 UTC\r
+Last updated 14-Apr-2007 16:21:44 UTC\r
</div>\r
</div>\r
</body>\r
</li>\r
<li>\r
<p>\r
+<em>%m</em>: left, right or boundary mark\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
<em>%n</em>: newline\r
</p>\r
<dl>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 04-Apr-2007 18:33:48 UTC\r
+Last updated 14-Apr-2007 16:21:45 UTC\r
</div>\r
</div>\r
</body>\r
[ --topo-order ]\r
[ --parents ]\r
[ --left-right ]\r
+ [ --cherry-pick ]\r
[ --encoding[=<encoding>] ]\r
[ --(author|committer|grep)=<pattern> ]\r
[ [--objects | --objects-edge] [ --unpacked ] ]\r
</li>\r
<li>\r
<p>\r
+<em>%m</em>: left, right or boundary mark\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
<em>%n</em>: newline\r
</p>\r
<dl>\r
</p>\r
</dd>\r
<dt>\r
+--cherry-pick\r
+</dt>\r
+<dd>\r
+<p>\r
+ Omit any commit that introduces the same change as\r
+ another commit on the "other side" when the set of\r
+ commits are limited with symmetric difference.<br />\r
+For example, if you have two branches, <tt>A</tt> and <tt>B</tt>, a usual way\r
+to list all commits on only one side of them is with\r
+<tt>--left-right</tt>, like the example above in the description of\r
+that option. It however shows the commits that were cherry-picked\r
+from the other branch (for example, "3rd on b" may be cherry-picked\r
+from branch A). With this option, such pairs of commits are\r
+excluded from the output.\r
+</p>\r
+</dd>\r
+<dt>\r
-g, --walk-reflogs\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 06-Apr-2007 00:51:16 UTC\r
+Last updated 14-Apr-2007 16:21:45 UTC\r
</div>\r
</div>\r
</body>\r
[ \--topo-order ]
[ \--parents ]
[ \--left-right ]
+ [ \--cherry-pick ]
[ \--encoding[=<encoding>] ]
[ \--(author|committer|grep)=<pattern> ]
[ [\--objects | \--objects-edge] [ \--unpacked ] ]
In addition to the '<commit>' listed on the command
line, read them from the standard input.
+--cherry-pick::
+
+ Omit any commit that introduces the same change as
+ another commit on the "other side" when the set of
+ commits are limited with symmetric difference.
++
+For example, if you have two branches, `A` and `B`, a usual way
+to list all commits on only one side of them is with
+`--left-right`, like the example above in the description of
+that option. It however shows the commits that were cherry-picked
+from the other branch (for example, "3rd on b" may be cherry-picked
+from branch A). With this option, such pairs of commits are
+excluded from the output.
+
-g, --walk-reflogs::
Instead of walking the commit ancestry chain, walk
</li>\r
<li>\r
<p>\r
+<em>%m</em>: left, right or boundary mark\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
<em>%n</em>: newline\r
</p>\r
<dl>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 04-Apr-2007 18:34:23 UTC\r
+Last updated 14-Apr-2007 16:21:46 UTC\r
</div>\r
</div>\r
</body>\r
- '%Cgreen': switch color to green
- '%Cblue': switch color to blue
- '%Creset': reset color
+- '%m': left, right or boundary mark
- '%n': newline