dissimilarity index <number>
index <hash>..<hash> <mode>
-3. TAB, LF, and backslash characters in pathnames are
- represented as `\t`, `\n`, and `\\`, respectively.
+3. TAB, LF, double quote and backslash characters in pathnames
+ are represented as `\t`, `\n`, `\"` and `\\`, respectively.
+ If there is need for such substitution then the whole
+ pathname is put in double quotes.
combined diff format
<h3>Examples</h3>\r
<dl>\r
<dt>\r
+We assume the following in /etc/services\r
+</dt>\r
+<dd>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>$ grep 9418 /etc/services\r
+git 9418/tcp # Git Version Control System</tt></pre>\r
+</div></div>\r
+</dd>\r
+<dt>\r
Run git-daemon to serve /pub/scm from inetd.\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 26-Oct-2006 08:47:21 UTC\r
+Last updated 27-Oct-2006 09:29:03 UTC\r
</div>\r
</div>\r
</body>\r
Examples
~~~~~~~~
+We assume the following in /etc/services::
++
+------------
+$ grep 9418 /etc/services
+git 9418/tcp # Git Version Control System
+------------
+
Run git-daemon to serve /pub/scm from inetd.::
+
------------
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-cherry</em> [-v] <upstream> [<head>]</p>\r
+<p><em>git-cherry</em> [-v] <upstream> [<head>] [<limit>]</p>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
has its id (sha1) reported, prefixed by a symbol. The ones that have\r
equivalent change already\r
in the <upstream> branch are prefixed with a minus (-) sign, and those\r
-that only exist in the <head> branch are prefixed with a plus (+) symbol.</p>\r
+that only exist in the <head> branch are prefixed with a plus (+) symbol:</p>\r
+<div class="literalblock">\r
+<div class="content">\r
+<pre><tt> __*__*__*__*__> <upstream>\r
+ /\r
+fork-point\r
+ \__+__+__-__+__+__-__+__> <head></tt></pre>\r
+</div></div>\r
+<p>If a <limit> has been given then the commits along the <head> branch up\r
+to and including <limit> are not reported:</p>\r
+<div class="literalblock">\r
+<div class="content">\r
+<pre><tt> __*__*__*__*__> <upstream>\r
+ /\r
+fork-point\r
+ \__*__*__<limit>__-__+__> <head></tt></pre>\r
+</div></div>\r
<p>Because git-cherry compares the changeset rather than the commit id\r
(sha1), you can use git-cherry to find out if a commit you made locally\r
has been applied <upstream> under a different commit id. For example,\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 25-Oct-2006 22:55:22 UTC\r
+Last updated 27-Oct-2006 09:28:58 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
-'git-cherry' [-v] <upstream> [<head>]
+'git-cherry' [-v] <upstream> [<head>] [<limit>]
DESCRIPTION
-----------
has its id (sha1) reported, prefixed by a symbol. The ones that have
equivalent change already
in the <upstream> branch are prefixed with a minus (-) sign, and those
-that only exist in the <head> branch are prefixed with a plus (+) symbol.
+that only exist in the <head> branch are prefixed with a plus (+) symbol:
+
+ __*__*__*__*__> <upstream>
+ /
+ fork-point
+ \__+__+__-__+__+__-__+__> <head>
+
+
+If a <limit> has been given then the commits along the <head> branch up
+to and including <limit> are not reported:
+
+ __*__*__*__*__> <upstream>
+ /
+ fork-point
+ \__*__*__<limit>__-__+__> <head>
+
Because git-cherry compares the changeset rather than the commit id
(sha1), you can use git-cherry to find out if a commit you made locally
from <tt>git-fetch</tt>, <tt>git-ls-remote</tt>, and <tt>git-clone</tt>.</p>\r
<p>This is ideally suited for read-only updates, i.e., pulling from\r
git repositories.</p>\r
+<p>An <tt>upload-archive</tt> also exists to serve <tt>git-archive</tt>.</p>\r
</div>\r
<h2>OPTIONS</h2>\r
<div class="sectionbody">\r
item to <tt>false</tt>.\r
</p>\r
</dd>\r
+<dt>\r
+upload-archive\r
+</dt>\r
+<dd>\r
+<p>\r
+ This serves <tt>git-archive --remote</tt>.\r
+</p>\r
+</dd>\r
</dl>\r
</div>\r
<h2>EXAMPLES</h2>\r
<div class="sectionbody">\r
<dl>\r
<dt>\r
+We assume the following in /etc/services\r
+</dt>\r
+<dd>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>$ grep 9418 /etc/services\r
+git 9418/tcp # Git Version Control System</tt></pre>\r
+</div></div>\r
+</dd>\r
+<dt>\r
git-daemon as inetd server\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 26-Oct-2006 08:47:15 UTC\r
+Last updated 27-Oct-2006 09:28:58 UTC\r
</div>\r
</div>\r
</body>\r
This is ideally suited for read-only updates, i.e., pulling from
git repositories.
+An `upload-archive` also exists to serve `git-archive`.
+
OPTIONS
-------
--strict-paths::
disable it by setting `daemon.uploadpack` configuration
item to `false`.
+upload-archive::
+ This serves `git-archive --remote`.
+
EXAMPLES
--------
+We assume the following in /etc/services::
++
+------------
+$ grep 9418 /etc/services
+git 9418/tcp # Git Version Control System
+------------
+
git-daemon as inetd server::
To set up `git-daemon` as an inetd service that handles any
repository under the whitelisted set of directories, /pub/foo
</li>\r
<li>\r
<p>\r
-TAB, LF, and backslash characters in pathnames are\r
- represented as <tt>\t</tt>, <tt>\n</tt>, and <tt>\\</tt>, respectively.\r
+TAB, LF, double quote and backslash characters in pathnames\r
+ are represented as <tt>\t</tt>, <tt>\n</tt>, <tt>\"</tt> and <tt>\\</tt>, respectively.\r
+ If there is need for such substitution then the whole\r
+ pathname is put in double quotes.\r
</p>\r
</li>\r
</ol>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 26-Oct-2006 08:47:16 UTC\r
+Last updated 27-Oct-2006 09:28:59 UTC\r
</div>\r
</div>\r
</body>\r
</li>\r
<li>\r
<p>\r
-TAB, LF, and backslash characters in pathnames are\r
- represented as <tt>\t</tt>, <tt>\n</tt>, and <tt>\\</tt>, respectively.\r
+TAB, LF, double quote and backslash characters in pathnames\r
+ are represented as <tt>\t</tt>, <tt>\n</tt>, <tt>\"</tt> and <tt>\\</tt>, respectively.\r
+ If there is need for such substitution then the whole\r
+ pathname is put in double quotes.\r
</p>\r
</li>\r
</ol>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 26-Oct-2006 08:47:17 UTC\r
+Last updated 27-Oct-2006 09:29:00 UTC\r
</div>\r
</div>\r
</body>\r
</li>\r
<li>\r
<p>\r
-TAB, LF, and backslash characters in pathnames are\r
- represented as <tt>\t</tt>, <tt>\n</tt>, and <tt>\\</tt>, respectively.\r
+TAB, LF, double quote and backslash characters in pathnames\r
+ are represented as <tt>\t</tt>, <tt>\n</tt>, <tt>\"</tt> and <tt>\\</tt>, respectively.\r
+ If there is need for such substitution then the whole\r
+ pathname is put in double quotes.\r
</p>\r
</li>\r
</ol>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 26-Oct-2006 08:47:18 UTC\r
+Last updated 27-Oct-2006 09:29:01 UTC\r
</div>\r
</div>\r
</body>\r
</li>\r
<li>\r
<p>\r
-TAB, LF, and backslash characters in pathnames are\r
- represented as <tt>\t</tt>, <tt>\n</tt>, and <tt>\\</tt>, respectively.\r
+TAB, LF, double quote and backslash characters in pathnames\r
+ are represented as <tt>\t</tt>, <tt>\n</tt>, <tt>\"</tt> and <tt>\\</tt>, respectively.\r
+ If there is need for such substitution then the whole\r
+ pathname is put in double quotes.\r
</p>\r
</li>\r
</ol>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 26-Oct-2006 08:47:19 UTC\r
+Last updated 27-Oct-2006 09:29:02 UTC\r
</div>\r
</div>\r
</body>\r