Tells `git-apply` how to handle whitespaces, in the same way
as the '--whitespace' option. See gitlink:git-apply[1].
+branch.<name>.remote::
+ When in branch <name>, it tells `git fetch` which remote to fetch.
+
+branch.<name>.merge::
+ When in branch <name>, it tells `git fetch` the default remote branch
+ to be merged.
+
pager.color::
A boolean to enable/disable colored output when the pager is in
use (default is true).
<div class="content"><em>git-daemon</em> [--verbose] [--syslog] [--inetd | --port=n] [--export-all]\r
[--timeout=n] [--init-timeout=n] [--strict-paths]\r
[--base-path=path] [--user-path | --user-path=path]\r
+ [--interpolated-path=pathtemplate]\r
[--enable=service] [--disable=service]\r
[--allow-override=service] [--forbid-override=service]\r
[--reuseaddr] [--detach] [--pid-file=file]\r
</p>\r
</dd>\r
<dt>\r
+--interpolated-path=pathtemplate\r
+</dt>\r
+<dd>\r
+<p>\r
+ To support virtual hosting, an interpolated path template can be\r
+ used to dynamically construct alternate paths. The template\r
+ supports %H for the target hostname as supplied by the client,\r
+ and %D for the absolute path of the named repository.\r
+</p>\r
+</dd>\r
+<dt>\r
--export-all\r
</dt>\r
<dd>\r
</dd>\r
</dl>\r
</div>\r
+<h2>EXAMPLES</h2>\r
+<div class="sectionbody">\r
+<dl>\r
+<dt>\r
+git-daemon as inetd server\r
+</dt>\r
+<dd>\r
+<p>\r
+ To set up <tt>git-daemon</tt> as an inetd service that handles any\r
+ repository under the whitelisted set of directories, /pub/foo\r
+ and /pub/bar, place an entry like the following into\r
+ /etc/inetd all on one line:\r
+</p>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt> git stream tcp nowait nobody /usr/bin/git-daemon\r
+ git-daemon --inetd --verbose\r
+ --syslog --export-all\r
+ /pub/foo /pub/bar</tt></pre>\r
+</div></div>\r
+</dd>\r
+<dt>\r
+git-daemon as inetd server for virtual hosts\r
+</dt>\r
+<dd>\r
+<p>\r
+ To set up <tt>git-daemon</tt> as an inetd service that handles\r
+ repositories for different virtual hosts, <tt>www.example.com</tt>\r
+ and <tt>www.example.org</tt>, place an entry like the following into\r
+ <tt>/etc/inetd</tt> all on one line:\r
+</p>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt> git stream tcp nowait nobody /usr/bin/git-daemon\r
+ git-daemon --inetd --verbose\r
+ --syslog --export-all\r
+ --interpolated-path=/pub/%H%D\r
+ /pub/www.example.org/software\r
+ /pub/www.example.com/software\r
+ /software</tt></pre>\r
+</div></div>\r
+<p>In this example, the root-level directory <tt>/pub</tt> will contain\r
+a subdirectory for each virtual host name supported.\r
+Further, both hosts advertise repositories simply as\r
+<tt>git://www.example.com/software/repo.git</tt>. For pre-1.4.0\r
+clients, a symlink from <tt>/software</tt> into the appropriate\r
+default repository could be made as well.</p>\r
+</dd>\r
+</dl>\r
+</div>\r
<h2>Author</h2>\r
<div class="sectionbody">\r
<p>Written by Linus Torvalds <torvalds@osdl.org>, YOSHIFUJI Hideaki\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Sep-2006 11:44:00 UTC\r
+Last updated 25-Sep-2006 04:45:33 UTC\r
</div>\r
</div>\r
</body>\r
'git-daemon' [--verbose] [--syslog] [--inetd | --port=n] [--export-all]
[--timeout=n] [--init-timeout=n] [--strict-paths]
[--base-path=path] [--user-path | --user-path=path]
+ [--interpolated-path=pathtemplate]
[--enable=service] [--disable=service]
[--allow-override=service] [--forbid-override=service]
[--reuseaddr] [--detach] [--pid-file=file]
'git://example.com/hello.git', `git-daemon` will interpret the path
as '/srv/git/hello.git'.
+--interpolated-path=pathtemplate::
+ To support virtual hosting, an interpolated path template can be
+ used to dynamically construct alternate paths. The template
+ supports %H for the target hostname as supplied by the client,
+ and %D for the absolute path of the named repository.
+
--export-all::
Allow pulling from all directories that look like GIT repositories
(have the 'objects' and 'refs' subdirectories), even if they
disable it by setting `daemon.uploadpack` configuration
item to `false`.
+EXAMPLES
+--------
+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
+ and /pub/bar, place an entry like the following into
+ /etc/inetd all on one line:
++
+------------------------------------------------
+ git stream tcp nowait nobody /usr/bin/git-daemon
+ git-daemon --inetd --verbose
+ --syslog --export-all
+ /pub/foo /pub/bar
+------------------------------------------------
+
+
+git-daemon as inetd server for virtual hosts::
+ To set up `git-daemon` as an inetd service that handles
+ repositories for different virtual hosts, `www.example.com`
+ and `www.example.org`, place an entry like the following into
+ `/etc/inetd` all on one line:
++
+------------------------------------------------
+ git stream tcp nowait nobody /usr/bin/git-daemon
+ git-daemon --inetd --verbose
+ --syslog --export-all
+ --interpolated-path=/pub/%H%D
+ /pub/www.example.org/software
+ /pub/www.example.com/software
+ /software
+------------------------------------------------
++
+In this example, the root-level directory `/pub` will contain
+a subdirectory for each virtual host name supported.
+Further, both hosts advertise repositories simply as
+`git://www.example.com/software/repo.git`. For pre-1.4.0
+clients, a symlink from `/software` into the appropriate
+default repository could be made as well.
+
+
Author
------
Written by Linus Torvalds <torvalds@osdl.org>, YOSHIFUJI Hideaki
</p>\r
</dd>\r
<dt>\r
+branch.<name>.remote\r
+</dt>\r
+<dd>\r
+<p>\r
+ When in branch <name>, it tells <tt>git fetch</tt> which remote to fetch.\r
+</p>\r
+</dd>\r
+<dt>\r
+branch.<name>.merge\r
+</dt>\r
+<dd>\r
+<p>\r
+ When in branch <name>, it tells <tt>git fetch</tt> the default remote branch\r
+ to be merged.\r
+</p>\r
+</dd>\r
+<dt>\r
pager.color\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 21-Sep-2006 08:13:18 UTC\r
+Last updated 25-Sep-2006 04:45:34 UTC\r
</div>\r
</div>\r
</body>\r
[ --stdin ]\r
[ --topo-order ]\r
[ --parents ]\r
+ [ --(author|committer|grep)=<pattern> ]\r
[ [--objects | --objects-edge] [ --unpacked ] ]\r
[ --pretty | --header ]\r
[ --bisect ]\r
</p>\r
</dd>\r
<dt>\r
+--author=<em>pattern</em>, --committer=<em>pattern</em>\r
+</dt>\r
+<dd>\r
+<p>\r
+ Limit the commits output to ones with author/committer\r
+ header lines that match the specified pattern.\r
+</p>\r
+</dd>\r
+<dt>\r
+--grep=<em>pattern</em>\r
+</dt>\r
+<dd>\r
+<p>\r
+ Limit the commits output to ones with log message that\r
+ matches the specified pattern.\r
+</p>\r
+</dd>\r
+<dt>\r
--remove-empty\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 06-Sep-2006 09:35:38 UTC\r
+Last updated 25-Sep-2006 04:45:35 UTC\r
</div>\r
</div>\r
</body>\r
[ \--stdin ]
[ \--topo-order ]
[ \--parents ]
+ [ \--(author|committer|grep)=<pattern> ]
[ [\--objects | \--objects-edge] [ \--unpacked ] ]
[ \--pretty | \--header ]
[ \--bisect ]
Limit the commits output to specified time range.
+--author='pattern', --committer='pattern'::
+
+ Limit the commits output to ones with author/committer
+ header lines that match the specified pattern.
+
+--grep='pattern'::
+
+ Limit the commits output to ones with log message that
+ matches the specified pattern.
+
--remove-empty::
Stop when a given path disappears from the tree.
doing.</p>\r
<p>repo-config key: svn.noignoreexternals</p>\r
</dd>\r
+<dt>\r
+--ignore-nodate\r
+</dt>\r
+<dd>\r
+<p>\r
+Only used with the <em>fetch</em> command.\r
+</p>\r
+<p>By default git-svn will crash if it tries to import a revision\r
+from SVN which has <em>(no date)</em> listed as the date of the revision.\r
+This is repository corruption on SVN's part, plain and simple.\r
+But sometimes you really need those revisions anyway.</p>\r
+<p>If supplied git-svn will convert <em>(no date)</em> entries to the UNIX\r
+epoch (midnight on Jan. 1, 1970). Yes, that's probably very wrong.\r
+SVN was very wrong.</p>\r
+</dd>\r
</dl>\r
<h3>Basic Examples</h3>\r
<p>Tracking and contributing to an Subversion managed-project:</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 26-Aug-2006 08:43:07 UTC\r
+Last updated 25-Sep-2006 04:45:35 UTC\r
</div>\r
</div>\r
</body>\r
repo-config key: svn.noignoreexternals
+--ignore-nodate::
+Only used with the 'fetch' command.
+
+By default git-svn will crash if it tries to import a revision
+from SVN which has '(no date)' listed as the date of the revision.
+This is repository corruption on SVN's part, plain and simple.
+But sometimes you really need those revisions anyway.
+
+If supplied git-svn will convert '(no date)' entries to the UNIX
+epoch (midnight on Jan. 1, 1970). Yes, that's probably very wrong.
+SVN was very wrong.
+
--
Basic Examples
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
+<p>THIS COMMAND IS DEPRECATED. Use <tt>git-archive</tt> with <tt>--format=tar</tt>\r
+option instead.</p>\r
<p>Creates a tar archive containing the tree structure for the named tree.\r
When <base> is specified it is added as a leading path to the files in the\r
generated tar archive.</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 31-Jul-2006 08:45:02 UTC\r
+Last updated 25-Sep-2006 04:45:36 UTC\r
</div>\r
</div>\r
</body>\r
DESCRIPTION
-----------
+THIS COMMAND IS DEPRECATED. Use `git-archive` with `--format=tar`
+option instead.
+
Creates a tar archive containing the tree structure for the named tree.
When <base> is specified it is added as a leading path to the files in the
generated tar archive.
+++ /dev/null
-git-upload-tar(1)
-=================
-
-NAME
-----
-git-upload-tar - Send tar archive
-
-
-SYNOPSIS
---------
-'git-upload-tar' <directory>
-
-DESCRIPTION
------------
-Invoked by 'git-tar-tree --remote' and sends a generated tar archive
-to the other end over the git protocol.
-
-This command is usually not invoked directly by the end user.
-The UI for the protocol is on the 'git-tar-tree' side, and the
-program pair is meant to be used to get a tar archive from a
-remote repository.
-
-
-OPTIONS
--------
-<directory>::
- The repository to get a tar archive from.
-
-Author
-------
-Written by Junio C Hamano <junio@kernel.org>
-
-Documentation
---------------
-Documentation by Junio C Hamano.
-
-GIT
----
-Part of the gitlink:git[7] suite
what are asked for.\r
</p>\r
</dd>\r
-<dt>\r
-<a href="git-upload-tar.html">git-upload-tar(1)</a>\r
-</dt>\r
-<dd>\r
-<p>\r
- Invoked by <em>git-tar-tree --remote</em> to return the tar\r
- archive the other end asked for.\r
-</p>\r
-</dd>\r
</dl>\r
</div>\r
<h2>High-level commands (porcelain)</h2>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 04-Sep-2006 10:08:24 UTC\r
+Last updated 25-Sep-2006 04:45:37 UTC\r
</div>\r
</div>\r
</body>\r
Invoked by 'git-fetch-pack' to push
what are asked for.
-gitlink:git-upload-tar[1]::
- Invoked by 'git-tar-tree --remote' to return the tar
- archive the other end asked for.
-
High-level commands (porcelain)
-------------------------------