one of `header` (the header text of the status message),
`added` or `updated` (files which are added but not committed),
`changed` (files which are changed but not added in the index),
- or `untracked` (files which are not tracked by git). The values of
- these variables may be specified as in color.branch.<slot>.
+ `untracked` (files which are not tracked by git), or
+ `nobranch` (the color the 'no branch' warning is shown in, defaulting
+ to red). The values of these variables may be specified as in
+ color.branch.<slot>.
commit.template::
Specify a file to use as the template for new commit messages.
The port number to bind the gitweb httpd to. See
linkgit:git-instaweb[1].
+log.date::
+ Set default date-time mode for the log command. Setting log.date
+ value is similar to using git log's --date option. The value is one of
+ following alternatives: {relative,local,default,iso,rfc,short}.
+ See linkgit:git-log[1].
+
log.showroot::
If true, the initial commit will be shown as a big creation event.
This is equivalent to a diff against an empty tree.
one of <tt>header</tt> (the header text of the status message),\r
<tt>added</tt> or <tt>updated</tt> (files which are added but not committed),\r
<tt>changed</tt> (files which are changed but not added in the index),\r
- or <tt>untracked</tt> (files which are not tracked by git). The values of\r
- these variables may be specified as in color.branch.<slot>.\r
+ <tt>untracked</tt> (files which are not tracked by git), or\r
+ <tt>nobranch</tt> (the color the <em>no branch</em> warning is shown in, defaulting\r
+ to red). The values of these variables may be specified as in\r
+ color.branch.<slot>.\r
</p>\r
</dd>\r
<dt>\r
</p>\r
</dd>\r
<dt>\r
+log.date\r
+</dt>\r
+<dd>\r
+<p>\r
+ Set default date-time mode for the log command. Setting log.date\r
+ value is similar to using git log's --date option. The value is one of\r
+ following alternatives: {relative,local,default,iso,rfc,short}.\r
+ See <a href="git-log.html">git-log(1)</a>.\r
+</p>\r
+</dd>\r
+<dt>\r
log.showroot\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 14-May-2008 22:24:40 UTC\r
+Last updated 24-May-2008 01:12:05 UTC\r
</div>\r
</div>\r
</body>\r
</p>\r
</dd>\r
<dt>\r
---date={relative,local,default,iso,rfc}\r
+--date={relative,local,default,iso,rfc,short}\r
</dt>\r
<dd>\r
<p>\r
Only takes effect for dates shown in human-readable format, such\r
- as when using "--pretty".\r
+ as when using "--pretty". <tt>log.date</tt> config variable sets a default\r
+ value for log command's --date option.\r
</p>\r
<p><tt>--date=relative</tt> shows dates relative to the current time,\r
e.g. "2 hours ago".</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 22-May-2008 00:52:46 UTC\r
+Last updated 24-May-2008 01:12:05 UTC\r
</div>\r
</div>\r
</body>\r
specified, the same ref that <src> referred to locally). If\r
the optional leading plus <tt>+</tt> is used, the remote ref is updated\r
even if it does not result in a fast forward update.</p>\r
-<p>Note: If no explicit refspec is found, (that is neither\r
-on the command line nor in any Push line of the\r
-corresponding remotes file---see below), then "matching" heads are\r
-pushed: for every head that exists on the local side, the remote side is\r
-updated if a head of the same name already exists on the remote side.</p>\r
<p><tt>tag <tag></tt> means the same as <tt>refs/tags/<tag>:refs/tags/<tag></tt>.</p>\r
<p>A parameter <ref> without a colon pushes the <ref> from the source\r
repository to the destination repository under the same name.</p>\r
<p>Pushing an empty <src> allows you to delete the <dst> ref from\r
the remote repository.</p>\r
+<p>The special refspec <tt>:</tt> (or <tt>+:</tt> to allow non-fast forward updates)\r
+directs git to push "matching" heads: for every head that exists on\r
+the local side, the remote side is updated if a head of the same name\r
+already exists on the remote side. This is the default operation mode\r
+if no explicit refspec is found (that is neither on the command line\r
+nor in any Push line of the corresponding remotes file---see below).</p>\r
</dd>\r
<dt>\r
--all\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 06-May-2008 06:34:59 UTC\r
+Last updated 24-May-2008 01:12:07 UTC\r
</div>\r
</div>\r
</body>\r
the optional leading plus `+` is used, the remote ref is updated
even if it does not result in a fast forward update.
+
-Note: If no explicit refspec is found, (that is neither
-on the command line nor in any Push line of the
-corresponding remotes file---see below), then "matching" heads are
-pushed: for every head that exists on the local side, the remote side is
-updated if a head of the same name already exists on the remote side.
-+
`tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`.
+
A parameter <ref> without a colon pushes the <ref> from the source
+
Pushing an empty <src> allows you to delete the <dst> ref from
the remote repository.
++
+The special refspec `:` (or `+:` to allow non-fast forward updates)
+directs git to push "matching" heads: for every head that exists on
+the local side, the remote side is updated if a head of the same name
+already exists on the remote side. This is the default operation mode
+if no explicit refspec is found (that is neither on the command line
+nor in any Push line of the corresponding remotes file---see below).
\--all::
Instead of naming each ref to push, specifies that all
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-repack</em> [-a] [-d] [-f] [-l] [-n] [-q] [--window=N] [--depth=N]</p>\r
+<p><em>git-repack</em> [-a] [-A] [-d] [-f] [-l] [-n] [-q] [--window=N] [--depth=N]</p>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
</p>\r
</dd>\r
<dt>\r
+-A\r
+</dt>\r
+<dd>\r
+<p>\r
+ Same as <tt>-a</tt>, but any unreachable objects in a previous\r
+ pack become loose, unpacked objects, instead of being\r
+ left in the old pack. Unreachable objects are never\r
+ intentionally added to a pack, even when repacking.\r
+ When used with <em>-d</em>, this option\r
+ prevents unreachable objects from being immediately\r
+ deleted by way of being left in the old pack and then\r
+ removed. Instead, the loose unreachable objects\r
+ will be pruned according to normal expiry rules\r
+ with the next <a href="git-gc.html">git-gc(1)</a>.\r
+</p>\r
+</dd>\r
+<dt>\r
-d\r
</dt>\r
<dd>\r
<dd>\r
<p>\r
Do not update the server information with\r
- <tt>git update-server-info</tt>.\r
+ <tt>git update-server-info</tt>. This option skips\r
+ updating local catalog files needed to publish\r
+ this repository (or a direct copy of it)\r
+ over HTTP or FTP. See .\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jan-2008 07:50:41 UTC\r
+Last updated 24-May-2008 01:12:07 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
-'git-repack' [-a] [-d] [-f] [-l] [-n] [-q] [--window=N] [--depth=N]
+'git-repack' [-a] [-A] [-d] [-f] [-l] [-n] [-q] [--window=N] [--depth=N]
DESCRIPTION
-----------
leaves behind, but `git fsck --full` shows as
dangling.
+-A::
+ Same as `-a`, but any unreachable objects in a previous
+ pack become loose, unpacked objects, instead of being
+ left in the old pack. Unreachable objects are never
+ intentionally added to a pack, even when repacking.
+ When used with '-d', this option
+ prevents unreachable objects from being immediately
+ deleted by way of being left in the old pack and then
+ removed. Instead, the loose unreachable objects
+ will be pruned according to normal expiry rules
+ with the next linkgit:git-gc[1].
+
-d::
After packing, if the newly created packs make some
existing packs redundant, remove the redundant packs.
linkgit:git-pack-objects[1].
-n::
- Do not update the server information with
- `git update-server-info`.
+ Do not update the server information with
+ `git update-server-info`. This option skips
+ updating local catalog files needed to publish
+ this repository (or a direct copy of it)
+ over HTTP or FTP. See gitlink:git-update-server-info[1].
--window=[N], --depth=[N]::
These two options affect how the objects contained in the pack are
</p>\r
</dd>\r
<dt>\r
---date={relative,local,default,iso,rfc}\r
+--date={relative,local,default,iso,rfc,short}\r
</dt>\r
<dd>\r
<p>\r
Only takes effect for dates shown in human-readable format, such\r
- as when using "--pretty".\r
+ as when using "--pretty". <tt>log.date</tt> config variable sets a default\r
+ value for log command's --date option.\r
</p>\r
<p><tt>--date=relative</tt> shows dates relative to the current time,\r
e.g. "2 hours ago".</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 22-May-2008 00:52:46 UTC\r
+Last updated 24-May-2008 01:12:07 UTC\r
</div>\r
</div>\r
</body>\r
<h2>Documentation</h2>\r
<div class="sectionbody">\r
<p>Documentation by David Greaves, Petr Baudis and the git-list <git@vger.kernel.org>.</p>\r
-<p>This manual page is a stub. You can help the git documentation by expanding it.</p>\r
</div>\r
<h2>GIT</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 09-Apr-2008 09:38:28 UTC\r
+Last updated 24-May-2008 01:12:08 UTC\r
</div>\r
</div>\r
</body>\r
-------------
Documentation by David Greaves, Petr Baudis and the git-list <git@vger.kernel.org>.
-This manual page is a stub. You can help the git documentation by expanding it.
-
GIT
---
Part of the linkgit:git[7] suite
Synonym for `--date=relative`.
---date={relative,local,default,iso,rfc}::
+--date={relative,local,default,iso,rfc,short}::
Only takes effect for dates shown in human-readable format, such
- as when using "--pretty".
+ as when using "--pretty". `log.date` config variable sets a default
+ value for log command's --date option.
+
`--date=relative` shows dates relative to the current time,
e.g. "2 hours ago".
projects / git.git / commitdiff