option values containing whitespace characters are currently not
supported.
+branch.<name>.rebase::
+ When true, rebase the branch <name> on top of the fetched branch,
+ instead of merging the default branch from the default remote.
+ *NOTE*: this is a possibly dangerous operation; do *not* use
+ it unless you understand the implications (see gitlink:git-rebase[1]
+ for details).
+
clean.requireForce::
A boolean to make git-clean do nothing unless given -f
or -n. Defaults to true.
<div class="verseblock">\r
<div class="content"><em>git-commit</em> [-a | --interactive] [-s] [-v] [-u]\r
[(-c | -C) <commit> | -F <file> | -m <msg> | --amend]\r
- [--no-verify] [-e] [--author <author>]\r
+ [--allow-empty] [--no-verify] [-e] [--author <author>]\r
[--] [[-i | -o ]<file>…]</div></div>\r
</div>\r
<h2>DESCRIPTION</h2>\r
</p>\r
</dd>\r
<dt>\r
+--allow-empty\r
+</dt>\r
+<dd>\r
+<p>\r
+ Usually recording a commit that has the exact same tree as its\r
+ sole parent commit and the command prevents you from making such\r
+ a mistake. This option bypasses the safety, and is primarily\r
+ for use by foreign scm interface scripts.\r
+</p>\r
+</dd>\r
+<dt>\r
-e|--edit\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 14-Nov-2007 12:11:25 UTC\r
+Last updated 03-Dec-2007 09:57:28 UTC\r
</div>\r
</div>\r
</body>\r
[verse]
'git-commit' [-a | --interactive] [-s] [-v] [-u]
[(-c | -C) <commit> | -F <file> | -m <msg> | --amend]
- [--no-verify] [-e] [--author <author>]
+ [--allow-empty] [--no-verify] [-e] [--author <author>]
[--] [[-i | -o ]<file>...]
DESCRIPTION
This option bypasses the pre-commit hook.
See also link:hooks.html[hooks].
+--allow-empty::
+ Usually recording a commit that has the exact same tree as its
+ sole parent commit and the command prevents you from making such
+ a mistake. This option bypasses the safety, and is primarily
+ for use by foreign scm interface scripts.
+
-e|--edit::
The message taken from file with `-F`, command line with
`-m`, and from file with `-C` are usually used as the
<em>git-config</em> [<file-option>] --unset-all name [value_regex]\r
<em>git-config</em> [<file-option>] --rename-section old_name new_name\r
<em>git-config</em> [<file-option>] --remove-section name\r
-<em>git-config</em> [<file-option>] [-z|--null] -l | --list</div></div>\r
+<em>git-config</em> [<file-option>] [-z|--null] -l | --list\r
+<em>git-config</em> [<file-option>] --get-color name [default]</div></div>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
contain line breaks.\r
</p>\r
</dd>\r
+<dt>\r
+--get-color name default\r
+</dt>\r
+<dd>\r
+<p>\r
+ Find the color configured for <tt>name</tt> (e.g. <tt>color.diff.new</tt>) and\r
+ output it as the ANSI color escape sequence to the standard\r
+ output. The optional <tt>default</tt> parameter is used instead, if\r
+ there is no color configured for <tt>name</tt>.\r
+</p>\r
+</dd>\r
</dl>\r
</div>\r
<h2><a id="FILES"></a>FILES</h2>\r
<div class="content">\r
<pre><tt>% git config core.gitproxy '"proxy-command" for example.com'</tt></pre>\r
</div></div>\r
+<p>An example to use customized color from the configuration in your\r
+script:</p>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>#!/bin/sh\r
+WS=$(git config --get-color color.diff.whitespace "blue reverse")\r
+RESET=$(git config --get-color "" "reset")\r
+echo "${WS}your whitespace color or blue reverse${RESET}"</tt></pre>\r
+</div></div>\r
</div>\r
<h2>CONFIGURATION FILE</h2>\r
<div class="sectionbody">\r
</p>\r
</dd>\r
<dt>\r
+branch.<name>.rebase\r
+</dt>\r
+<dd>\r
+<p>\r
+ When true, rebase the branch <name> on top of the fetched branch,\r
+ instead of merging the default branch from the default remote.\r
+ <strong>NOTE</strong>: this is a possibly dangerous operation; do <strong>not</strong> use\r
+ it unless you understand the implications (see <a href="git-rebase.html">git-rebase(1)</a>\r
+ for details).\r
+</p>\r
+</dd>\r
+<dt>\r
clean.requireForce\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 21-Nov-2007 08:54:16 UTC\r
+Last updated 03-Dec-2007 09:57:28 UTC\r
</div>\r
</div>\r
</body>\r
'git-config' [<file-option>] --rename-section old_name new_name
'git-config' [<file-option>] --remove-section name
'git-config' [<file-option>] [-z|--null] -l | --list
+'git-config' [<file-option>] --get-color name [default]
DESCRIPTION
-----------
output without getting confused e.g. by values that
contain line breaks.
+--get-color name default::
+
+ Find the color configured for `name` (e.g. `color.diff.new`) and
+ output it as the ANSI color escape sequence to the standard
+ output. The optional `default` parameter is used instead, if
+ there is no color configured for `name`.
[[FILES]]
FILES
% git config core.gitproxy '"proxy-command" for example.com'
------------
+An example to use customized color from the configuration in your
+script:
+
+------------
+#!/bin/sh
+WS=$(git config --get-color color.diff.whitespace "blue reverse")
+RESET=$(git config --get-color "" "reset")
+echo "${WS}your whitespace color or blue reverse${RESET}"
+------------
include::config.txt[]
--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"\r
+ "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">\r
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">\r
+<head>\r
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />\r
+<meta name="generator" content="AsciiDoc 7.0.2" />\r
+<style type="text/css">\r
+/* Debug borders */\r
+p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {\r
+/*\r
+ border: 1px solid red;\r
+*/\r
+}\r
+\r
+body {\r
+ margin: 1em 5% 1em 5%;\r
+}\r
+\r
+a { color: blue; }\r
+a:visited { color: fuchsia; }\r
+\r
+em {\r
+ font-style: italic;\r
+}\r
+\r
+strong {\r
+ font-weight: bold;\r
+}\r
+\r
+tt {\r
+ color: navy;\r
+}\r
+\r
+h1, h2, h3, h4, h5, h6 {\r
+ color: #527bbd;\r
+ font-family: sans-serif;\r
+ margin-top: 1.2em;\r
+ margin-bottom: 0.5em;\r
+ line-height: 1.3;\r
+}\r
+\r
+h1 {\r
+ border-bottom: 2px solid silver;\r
+}\r
+h2 {\r
+ border-bottom: 2px solid silver;\r
+ padding-top: 0.5em;\r
+}\r
+\r
+div.sectionbody {\r
+ font-family: serif;\r
+ margin-left: 0;\r
+}\r
+\r
+hr {\r
+ border: 1px solid silver;\r
+}\r
+\r
+p {\r
+ margin-top: 0.5em;\r
+ margin-bottom: 0.5em;\r
+}\r
+\r
+pre {\r
+ padding: 0;\r
+ margin: 0;\r
+}\r
+\r
+span#author {\r
+ color: #527bbd;\r
+ font-family: sans-serif;\r
+ font-weight: bold;\r
+ font-size: 1.2em;\r
+}\r
+span#email {\r
+}\r
+span#revision {\r
+ font-family: sans-serif;\r
+}\r
+\r
+div#footer {\r
+ font-family: sans-serif;\r
+ font-size: small;\r
+ border-top: 2px solid silver;\r
+ padding-top: 0.5em;\r
+ margin-top: 4.0em;\r
+}\r
+div#footer-text {\r
+ float: left;\r
+ padding-bottom: 0.5em;\r
+}\r
+div#footer-badges {\r
+ float: right;\r
+ padding-bottom: 0.5em;\r
+}\r
+\r
+div#preamble,\r
+div.tableblock, div.imageblock, div.exampleblock, div.verseblock,\r
+div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,\r
+div.admonitionblock {\r
+ margin-right: 10%;\r
+ margin-top: 1.5em;\r
+ margin-bottom: 1.5em;\r
+}\r
+div.admonitionblock {\r
+ margin-top: 2.5em;\r
+ margin-bottom: 2.5em;\r
+}\r
+\r
+div.content { /* Block element content. */\r
+ padding: 0;\r
+}\r
+\r
+/* Block element titles. */\r
+div.title, caption.title {\r
+ font-family: sans-serif;\r
+ font-weight: bold;\r
+ text-align: left;\r
+ margin-top: 1.0em;\r
+ margin-bottom: 0.5em;\r
+}\r
+div.title + * {\r
+ margin-top: 0;\r
+}\r
+\r
+td div.title:first-child {\r
+ margin-top: 0.0em;\r
+}\r
+div.content div.title:first-child {\r
+ margin-top: 0.0em;\r
+}\r
+div.content + div.title {\r
+ margin-top: 0.0em;\r
+}\r
+\r
+div.sidebarblock > div.content {\r
+ background: #ffffee;\r
+ border: 1px solid silver;\r
+ padding: 0.5em;\r
+}\r
+\r
+div.listingblock > div.content {\r
+ border: 1px solid silver;\r
+ background: #f4f4f4;\r
+ padding: 0.5em;\r
+}\r
+\r
+div.quoteblock > div.content {\r
+ padding-left: 2.0em;\r
+}\r
+div.quoteblock .attribution {\r
+ text-align: right;\r
+}\r
+\r
+div.admonitionblock .icon {\r
+ vertical-align: top;\r
+ font-size: 1.1em;\r
+ font-weight: bold;\r
+ text-decoration: underline;\r
+ color: #527bbd;\r
+ padding-right: 0.5em;\r
+}\r
+div.admonitionblock td.content {\r
+ padding-left: 0.5em;\r
+ border-left: 2px solid silver;\r
+}\r
+\r
+div.exampleblock > div.content {\r
+ border-left: 2px solid silver;\r
+ padding: 0.5em;\r
+}\r
+\r
+div.verseblock div.content {\r
+ white-space: pre;\r
+}\r
+\r
+div.imageblock div.content { padding-left: 0; }\r
+div.imageblock img { border: 1px solid silver; }\r
+span.image img { border-style: none; }\r
+\r
+dl {\r
+ margin-top: 0.8em;\r
+ margin-bottom: 0.8em;\r
+}\r
+dt {\r
+ margin-top: 0.5em;\r
+ margin-bottom: 0;\r
+ font-style: italic;\r
+}\r
+dd > *:first-child {\r
+ margin-top: 0;\r
+}\r
+\r
+ul, ol {\r
+ list-style-position: outside;\r
+}\r
+ol.olist2 {\r
+ list-style-type: lower-alpha;\r
+}\r
+\r
+div.tableblock > table {\r
+ border-color: #527bbd;\r
+ border-width: 3px;\r
+}\r
+thead {\r
+ font-family: sans-serif;\r
+ font-weight: bold;\r
+}\r
+tfoot {\r
+ font-weight: bold;\r
+}\r
+\r
+div.hlist {\r
+ margin-top: 0.8em;\r
+ margin-bottom: 0.8em;\r
+}\r
+td.hlist1 {\r
+ vertical-align: top;\r
+ font-style: italic;\r
+ padding-right: 0.8em;\r
+}\r
+td.hlist2 {\r
+ vertical-align: top;\r
+}\r
+\r
+@media print {\r
+ div#footer-badges { display: none; }\r
+}\r
+include::./stylesheets/xhtml11-manpage.css[]\r
+/* Workarounds for IE6's broken and incomplete CSS2. */\r
+\r
+div.sidebar-content {\r
+ background: #ffffee;\r
+ border: 1px solid silver;\r
+ padding: 0.5em;\r
+}\r
+div.sidebar-title, div.image-title {\r
+ font-family: sans-serif;\r
+ font-weight: bold;\r
+ margin-top: 0.0em;\r
+ margin-bottom: 0.5em;\r
+}\r
+\r
+div.listingblock div.content {\r
+ border: 1px solid silver;\r
+ background: #f4f4f4;\r
+ padding: 0.5em;\r
+}\r
+\r
+div.quoteblock-content {\r
+ padding-left: 2.0em;\r
+}\r
+\r
+div.exampleblock-content {\r
+ border-left: 2px solid silver;\r
+ padding-left: 0.5em;\r
+}\r
+</style>\r
+<title>git-fast-export(1)</title>\r
+</head>\r
+<body>\r
+<div id="header">\r
+<h1>\r
+git-fast-export(1) Manual Page\r
+</h1>\r
+<h2>NAME</h2>\r
+<div class="sectionbody">\r
+<p>git-fast-export -\r
+ Git data exporter\r
+</p>\r
+</div>\r
+</div>\r
+<h2>SYNOPSIS</h2>\r
+<div class="sectionbody">\r
+<p><em>git-fast-export [options]</em> | <em>git-fast-import</em></p>\r
+</div>\r
+<h2>DESCRIPTION</h2>\r
+<div class="sectionbody">\r
+<p>This program dumps the given revisions in a form suitable to be piped\r
+into <a href="git-fast-import.html">git-fast-import(1)</a>.</p>\r
+<p>You can use it as a human readable bundle replacement (see\r
+<a href="git-bundle.html">git-bundle(1)</a>), or as a kind of an interactive\r
+<a href="git-filter-branch.html">git-filter-branch(1)</a>.</p>\r
+</div>\r
+<h2>OPTIONS</h2>\r
+<div class="sectionbody">\r
+<dl>\r
+<dt>\r
+--progress=<n>\r
+</dt>\r
+<dd>\r
+<p>\r
+ Insert <em>progress</em> statements every <n> objects, to be shown by\r
+ <a href="git-fast-import.html">git-fast-import(1)</a> during import.\r
+</p>\r
+</dd>\r
+<dt>\r
+--signed-tags=(ignore|warn|strip|abort)\r
+</dt>\r
+<dd>\r
+<p>\r
+ Specify how to handle signed tags. Since any transformation\r
+ after the export can change the tag names (which can also happen\r
+ when excluding revisions) the signatures will not match.\r
+</p>\r
+<p>When asking to <em>abort</em> (which is the default), this program will die\r
+when encountering a signed tag. With <em>strip</em>, the tags will be made\r
+unsigned, with <em>ignore</em>, they will be silently ignored (i.e. not exported)\r
+and with <em>warn</em>, they will be exported, but you will see a warning.</p>\r
+</dd>\r
+</dl>\r
+</div>\r
+<h2>EXAMPLES</h2>\r
+<div class="sectionbody">\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>$ git fast-export --all | (cd /empty/repository && git fast-import)</tt></pre>\r
+</div></div>\r
+<p>This will export the whole repository and import it into the existing\r
+empty repository. Except for reencoding commits that are not in\r
+UTF-8, it would be a one-to-one mirror.</p>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>$ git fast-export master~5..master |\r
+ sed "s|refs/heads/master|refs/heads/other|" |\r
+ git fast-import</tt></pre>\r
+</div></div>\r
+<p>This makes a new branch called <em>other</em> from <em>master~5..master</em>\r
+(i.e. if <em>master</em> has linear history, it will take the last 5 commits).</p>\r
+<p>Note that this assumes that none of the blobs and commit messages\r
+referenced by that revision range contains the string\r
+<em>refs/heads/master</em>.</p>\r
+</div>\r
+<h2>Limitations</h2>\r
+<div class="sectionbody">\r
+<p>Since <a href="git-fast-import.html">git-fast-import(1)</a> cannot tag trees, you will not be\r
+able to export the linux-2.6.git repository completely, as it contains\r
+a tag referencing a tree instead of a commit.</p>\r
+</div>\r
+<h2>Author</h2>\r
+<div class="sectionbody">\r
+<p>Written by Johannes E. Schindelin <johannes.schindelin@gmx.de>.</p>\r
+</div>\r
+<h2>Documentation</h2>\r
+<div class="sectionbody">\r
+<p>Documentation by Johannes E. Schindelin <johannes.schindelin@gmx.de>.</p>\r
+</div>\r
+<h2>GIT</h2>\r
+<div class="sectionbody">\r
+<p>Part of the <a href="git.html">git(7)</a> suite</p>\r
+</div>\r
+<div id="footer">\r
+<div id="footer-text">\r
+Last updated 03-Dec-2007 09:57:29 UTC\r
+</div>\r
+</div>\r
+</body>\r
+</html>\r
--- /dev/null
+git-fast-export(1)
+==================
+
+NAME
+----
+git-fast-export - Git data exporter
+
+
+SYNOPSIS
+--------
+'git-fast-export [options]' | 'git-fast-import'
+
+DESCRIPTION
+-----------
+This program dumps the given revisions in a form suitable to be piped
+into gitlink:git-fast-import[1].
+
+You can use it as a human readable bundle replacement (see
+gitlink:git-bundle[1]), or as a kind of an interactive
+gitlink:git-filter-branch[1].
+
+
+OPTIONS
+-------
+--progress=<n>::
+ Insert 'progress' statements every <n> objects, to be shown by
+ gitlink:git-fast-import[1] during import.
+
+--signed-tags=(ignore|warn|strip|abort)::
+ Specify how to handle signed tags. Since any transformation
+ after the export can change the tag names (which can also happen
+ when excluding revisions) the signatures will not match.
++
+When asking to 'abort' (which is the default), this program will die
+when encountering a signed tag. With 'strip', the tags will be made
+unsigned, with 'ignore', they will be silently ignored (i.e. not exported)
+and with 'warn', they will be exported, but you will see a warning.
+
+
+EXAMPLES
+--------
+
+-------------------------------------------------------------------
+$ git fast-export --all | (cd /empty/repository && git fast-import)
+-------------------------------------------------------------------
+
+This will export the whole repository and import it into the existing
+empty repository. Except for reencoding commits that are not in
+UTF-8, it would be a one-to-one mirror.
+
+-----------------------------------------------------
+$ git fast-export master~5..master |
+ sed "s|refs/heads/master|refs/heads/other|" |
+ git fast-import
+-----------------------------------------------------
+
+This makes a new branch called 'other' from 'master~5..master'
+(i.e. if 'master' has linear history, it will take the last 5 commits).
+
+Note that this assumes that none of the blobs and commit messages
+referenced by that revision range contains the string
+'refs/heads/master'.
+
+
+Limitations
+-----------
+
+Since gitlink:git-fast-import[1] cannot tag trees, you will not be
+able to export the linux-2.6.git repository completely, as it contains
+a tag referencing a tree instead of a commit.
+
+
+Author
+------
+Written by Johannes E. Schindelin <johannes.schindelin@gmx.de>.
+
+Documentation
+--------------
+Documentation by Johannes E. Schindelin <johannes.schindelin@gmx.de>.
+
+GIT
+---
+Part of the gitlink:git[7] suite
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-prune</em> [-n] [--] [<head>…]</p>\r
+<p><em>git-prune</em> [-n] [--expire <expire>] [--] [<head>…]</p>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
</p>\r
</dd>\r
<dt>\r
+--expire <time>\r
+</dt>\r
+<dd>\r
+<p>\r
+ Only expire loose objects older than <time>.\r
+</p>\r
+</dd>\r
+<dt>\r
<head>…\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 14-Nov-2007 12:11:41 UTC\r
+Last updated 03-Dec-2007 09:57:29 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
-'git-prune' [-n] [--] [<head>...]
+'git-prune' [-n] [--expire <expire>] [--] [<head>...]
DESCRIPTION
-----------
\--::
Do not interpret any more arguments as options.
+\--expire <time>::
+ Only expire loose objects older than <time>.
+
<head>...::
In addition to objects
reachable from any of our references, keep objects
branches.\r
</p>\r
</dd>\r
+<dt>\r
+--rebase\r
+</dt>\r
+<dd>\r
+<p>\r
+ Instead of a merge, perform a rebase after fetching.\r
+ <strong>NOTE:</strong> This is a potentially _dangerous_ mode of operation.\r
+ It rewrites history, which does not bode well when you\r
+ published that history already. Do <strong>not</strong> use this option\r
+ unless you have read <a href="git-rebase.html">git-rebase(1)</a> carefully.\r
+</p>\r
+</dd>\r
+<dt>\r
+--no-rebase\r
+</dt>\r
+<dd>\r
+<p>\r
+ Override earlier --rebase.\r
+</p>\r
+</dd>\r
</dl>\r
</div>\r
<h2>DEFAULT BEHAVIOUR</h2>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 17-Nov-2007 20:50:31 UTC\r
+Last updated 03-Dec-2007 09:57:29 UTC\r
</div>\r
</div>\r
</body>\r
include::merge-strategies.txt[]
+\--rebase::
+ Instead of a merge, perform a rebase after fetching.
+ *NOTE:* This is a potentially _dangerous_ mode of operation.
+ It rewrites history, which does not bode well when you
+ published that history already. Do *not* use this option
+ unless you have read gitlink:git-rebase[1] carefully.
+
+\--no-rebase::
+ Override earlier \--rebase.
+
DEFAULT BEHAVIOUR
-----------------