assigns blame to the lines that were moved down (i.e. A)
to the child commit. With this option, both groups of lines
are blamed on the parent.
-
- <num> is optional but it is the lower bound on the number of
- alphanumeric characters that git must detect as moving
- within a file for it to associate those lines with the parent
- commit.
++
+<num> is optional but it is the lower bound on the number of
+alphanumeric characters that git must detect as moving
+within a file for it to associate those lines with the parent
+commit.
-C|<num>|::
In addition to `-M`, detect lines copied from other
around across files. When this option is given twice,
the command looks for copies from all other files in the
parent for the commit that creates the file in addition.
-
- <num> is optional but it is the lower bound on the number of
- alphanumeric characters that git must detect as moving
- between files for it to associate those lines with the parent
- commit.
++
+<num> is optional but it is the lower bound on the number of
+alphanumeric characters that git must detect as moving
+between files for it to associate those lines with the parent
+commit.
-h, --help::
Show help message.
Show branches and their commits.
gitlink:git-verify-tag[1]::
- Check the GPG signature of tag.
+ Check the GPG signature of tags.
gitlink:git-whatchanged[1]::
Show logs with difference each commit introduces.
+gitlink:git-config[1]::
+ Get and set repository or global options.
+
gitlink:git-convert-objects[1]::
Converts old-style git repository.
gitlink:git-relink[1]::
Hardlink common objects in local repositories.
-gitlink:git-repack[1]::
- Pack unpacked objects in a repository.
-
-gitlink:git-config[1]::
- Get and set repository or global options.
-
gitlink:git-remote[1]::
manage set of tracked repositories.
+gitlink:git-repack[1]::
+ Pack unpacked objects in a repository.
+
to the child commit. With this option, both groups of lines\r
are blamed on the parent.\r
</p>\r
-<div class="literalblock">\r
-<div class="content">\r
-<pre><tt><num> is optional but it is the lower bound on the number of\r
+<p><num> is optional but it is the lower bound on the number of\r
alphanumeric characters that git must detect as moving\r
within a file for it to associate those lines with the parent\r
-commit.</tt></pre>\r
-</div></div>\r
+commit.</p>\r
</dd>\r
<dt>\r
-C|<num>|\r
the command looks for copies from all other files in the\r
parent for the commit that creates the file in addition.\r
</p>\r
-<div class="literalblock">\r
-<div class="content">\r
-<pre><tt><num> is optional but it is the lower bound on the number of\r
+<p><num> is optional but it is the lower bound on the number of\r
alphanumeric characters that git must detect as moving\r
between files for it to associate those lines with the parent\r
-commit.</tt></pre>\r
-</div></div>\r
+commit.</p>\r
</dd>\r
<dt>\r
-h, --help\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:31 UTC\r
+Last updated 10-Aug-2007 09:49:28 UTC\r
</div>\r
</div>\r
</body>\r
to the child commit. With this option, both groups of lines\r
are blamed on the parent.\r
</p>\r
-<div class="literalblock">\r
-<div class="content">\r
-<pre><tt><num> is optional but it is the lower bound on the number of\r
+<p><num> is optional but it is the lower bound on the number of\r
alphanumeric characters that git must detect as moving\r
within a file for it to associate those lines with the parent\r
-commit.</tt></pre>\r
-</div></div>\r
+commit.</p>\r
</dd>\r
<dt>\r
-C|<num>|\r
the command looks for copies from all other files in the\r
parent for the commit that creates the file in addition.\r
</p>\r
-<div class="literalblock">\r
-<div class="content">\r
-<pre><tt><num> is optional but it is the lower bound on the number of\r
+<p><num> is optional but it is the lower bound on the number of\r
alphanumeric characters that git must detect as moving\r
between files for it to associate those lines with the parent\r
-commit.</tt></pre>\r
-</div></div>\r
+commit.</p>\r
</dd>\r
<dt>\r
-h, --help\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:32 UTC\r
+Last updated 10-Aug-2007 09:49:28 UTC\r
</div>\r
</div>\r
</body>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
<div class="verseblock">\r
-<div class="content"><em>git-clone</em> [--template=<template_directory>] [-l [-s]] [-q] [-n] [--bare]\r
+<div class="content"><em>git-clone</em> [--template=<template_directory>]\r
+ [-l] [-s] [--no-hardlinks] [-q] [-n] [--bare]\r
[-o <name>] [-u <upload-pack>] [--reference <repository>]\r
[--depth <depth>] <repository> [<directory>]</div></div>\r
</div>\r
this flag bypasses normal "git aware" transport\r
mechanism and clones the repository by making a copy of\r
HEAD and everything under objects and refs directories.\r
- The files under .git/objects/ directory are hardlinked\r
- to save space when possible.\r
+ The files under <tt>.git/objects/</tt> directory are hardlinked\r
+ to save space when possible. This is now the default when\r
+ the source repository is specified with <tt>/path/to/repo</tt>\r
+ syntax, so it essentially is a no-op option. To force\r
+ copying instead of hardlinking (which may be desirable\r
+ if you are trying to make a back-up of your repository),\r
+ but still avoid the usual "git aware" transport\r
+ mechanism, <tt>--no-hardlinks</tt> can be used.\r
+</p>\r
+</dd>\r
+<dt>\r
+--no-hardlinks\r
+</dt>\r
+<dd>\r
+<p>\r
+ Optimize the cloning process from a repository on a\r
+ local filesystem by copying files under <tt>.git/objects</tt>\r
+ directory.\r
</p>\r
</dd>\r
<dt>\r
</li>\r
</ul>\r
</div></div>\r
-<p>SSH is the default transport protocol. You can optionally specify\r
-which user to log-in as, and an alternate, scp-like syntax is also\r
-supported. Both syntaxes support username expansion,\r
-as does the native git protocol. The following three are\r
-identical to the last three above, respectively:</p>\r
+<p>SSH is the default transport protocol over the network. You can\r
+optionally specify which user to log-in as, and an alternate,\r
+scp-like syntax is also supported. Both syntaxes support\r
+username expansion, as does the native git protocol. The following\r
+three are identical to the last three above, respectively:</p>\r
<div class="exampleblock">\r
<div class="exampleblock-content">\r
<ul>\r
</li>\r
</ul>\r
</div></div>\r
-<p>To sync with a local directory, use:</p>\r
+<p>To sync with a local directory, you can use:</p>\r
<div class="exampleblock">\r
<div class="exampleblock-content">\r
<ul>\r
/path/to/repo.git/\r
</p>\r
</li>\r
+<li>\r
+<p>\r
+file:///path/to/repo.git/\r
+</p>\r
+</li>\r
</ul>\r
</div></div>\r
+<p>They are mostly equivalent, except when cloning. See\r
+<a href="git-clone.html">git-clone(1)</a> for details.</p>\r
</div>\r
<h2>Examples</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:34 UTC\r
+Last updated 11-Aug-2007 08:29:13 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
[verse]
-'git-clone' [--template=<template_directory>] [-l [-s]] [-q] [-n] [--bare]
+'git-clone' [--template=<template_directory>]
+ [-l] [-s] [--no-hardlinks] [-q] [-n] [--bare]
[-o <name>] [-u <upload-pack>] [--reference <repository>]
[--depth <depth>] <repository> [<directory>]
this flag bypasses normal "git aware" transport
mechanism and clones the repository by making a copy of
HEAD and everything under objects and refs directories.
- The files under .git/objects/ directory are hardlinked
- to save space when possible.
+ The files under `.git/objects/` directory are hardlinked
+ to save space when possible. This is now the default when
+ the source repository is specified with `/path/to/repo`
+ syntax, so it essentially is a no-op option. To force
+ copying instead of hardlinking (which may be desirable
+ if you are trying to make a back-up of your repository),
+ but still avoid the usual "git aware" transport
+ mechanism, `--no-hardlinks` can be used.
+
+--no-hardlinks::
+ Optimize the cloning process from a repository on a
+ local filesystem by copying files under `.git/objects`
+ directory.
--shared::
-s::
</li>\r
</ul>\r
</div></div>\r
-<p>SSH is the default transport protocol. You can optionally specify\r
-which user to log-in as, and an alternate, scp-like syntax is also\r
-supported. Both syntaxes support username expansion,\r
-as does the native git protocol. The following three are\r
-identical to the last three above, respectively:</p>\r
+<p>SSH is the default transport protocol over the network. You can\r
+optionally specify which user to log-in as, and an alternate,\r
+scp-like syntax is also supported. Both syntaxes support\r
+username expansion, as does the native git protocol. The following\r
+three are identical to the last three above, respectively:</p>\r
<div class="exampleblock">\r
<div class="exampleblock-content">\r
<ul>\r
</li>\r
</ul>\r
</div></div>\r
-<p>To sync with a local directory, use:</p>\r
+<p>To sync with a local directory, you can use:</p>\r
<div class="exampleblock">\r
<div class="exampleblock-content">\r
<ul>\r
/path/to/repo.git/\r
</p>\r
</li>\r
+<li>\r
+<p>\r
+file:///path/to/repo.git/\r
+</p>\r
+</li>\r
</ul>\r
</div></div>\r
+<p>They are mostly equivalent, except when cloning. See\r
+<a href="git-clone.html">git-clone(1)</a> for details.</p>\r
</div>\r
<h2>REMOTES</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:40 UTC\r
+Last updated 11-Aug-2007 08:29:13 UTC\r
</div>\r
</div>\r
</body>\r
</li>\r
</ul>\r
</div></div>\r
-<p>SSH is the default transport protocol. You can optionally specify\r
-which user to log-in as, and an alternate, scp-like syntax is also\r
-supported. Both syntaxes support username expansion,\r
-as does the native git protocol. The following three are\r
-identical to the last three above, respectively:</p>\r
+<p>SSH is the default transport protocol over the network. You can\r
+optionally specify which user to log-in as, and an alternate,\r
+scp-like syntax is also supported. Both syntaxes support\r
+username expansion, as does the native git protocol. The following\r
+three are identical to the last three above, respectively:</p>\r
<div class="exampleblock">\r
<div class="exampleblock-content">\r
<ul>\r
</li>\r
</ul>\r
</div></div>\r
-<p>To sync with a local directory, use:</p>\r
+<p>To sync with a local directory, you can use:</p>\r
<div class="exampleblock">\r
<div class="exampleblock-content">\r
<ul>\r
/path/to/repo.git/\r
</p>\r
</li>\r
+<li>\r
+<p>\r
+file:///path/to/repo.git/\r
+</p>\r
+</li>\r
</ul>\r
</div></div>\r
+<p>They are mostly equivalent, except when cloning. See\r
+<a href="git-clone.html">git-clone(1)</a> for details.</p>\r
</div>\r
<h2>REMOTES</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:49 UTC\r
+Last updated 11-Aug-2007 08:29:14 UTC\r
</div>\r
</div>\r
</body>\r
</li>\r
</ul>\r
</div></div>\r
-<p>SSH is the default transport protocol. You can optionally specify\r
-which user to log-in as, and an alternate, scp-like syntax is also\r
-supported. Both syntaxes support username expansion,\r
-as does the native git protocol. The following three are\r
-identical to the last three above, respectively:</p>\r
+<p>SSH is the default transport protocol over the network. You can\r
+optionally specify which user to log-in as, and an alternate,\r
+scp-like syntax is also supported. Both syntaxes support\r
+username expansion, as does the native git protocol. The following\r
+three are identical to the last three above, respectively:</p>\r
<div class="exampleblock">\r
<div class="exampleblock-content">\r
<ul>\r
</li>\r
</ul>\r
</div></div>\r
-<p>To sync with a local directory, use:</p>\r
+<p>To sync with a local directory, you can use:</p>\r
<div class="exampleblock">\r
<div class="exampleblock-content">\r
<ul>\r
/path/to/repo.git/\r
</p>\r
</li>\r
+<li>\r
+<p>\r
+file:///path/to/repo.git/\r
+</p>\r
+</li>\r
</ul>\r
</div></div>\r
+<p>They are mostly equivalent, except when cloning. See\r
+<a href="git-clone.html">git-clone(1)</a> for details.</p>\r
</div>\r
<h2>REMOTES</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 06-Aug-2007 04:38:48 UTC\r
+Last updated 11-Aug-2007 08:29:14 UTC\r
</div>\r
</div>\r
</body>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:52 UTC\r
+Last updated 10-Aug-2007 09:49:28 UTC\r
</div>\r
</div>\r
</body>\r
G H I J
\ / \ /
D E F
- \ | / \
+ \ | / \
\ | / |
\|/ |
B C
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-stripspace</em> < <stream></p>\r
+<p><em>git-stripspace</em> [-s | --strip-comments] < <stream></p>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
<div class="sectionbody">\r
<dl>\r
<dt>\r
+-s\|--strip-comments\r
+</dt>\r
+<dd>\r
+<p>\r
+ In addition to empty lines, also strip lines starting with <em>#</em>.\r
+</p>\r
+</dd>\r
+<dt>\r
<stream>\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:56 UTC\r
+Last updated 11-Aug-2007 08:29:16 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
-'git-stripspace' < <stream>
+'git-stripspace' [-s | --strip-comments] < <stream>
DESCRIPTION
-----------
OPTIONS
-------
+-s\|--strip-comments::
+ In addition to empty lines, also strip lines starting with '#'.
+
<stream>::
Byte stream to act on.
<div class="content"><em>git-tag</em> [-a | -s | -u <key-id>] [-f] [-m <msg> | -F <file>] <name> [<head>]\r
<em>git-tag</em> -d <name>…\r
<em>git-tag</em> [-n [<num>]] -l [<pattern>]\r
-<em>git-tag</em> -v <name></div></div>\r
+<em>git-tag</em> -v <name>…</div></div>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
<tt>.git/refs/tags/</tt> directory.</p>\r
<p>If one of <tt>-a</tt>, <tt>-s</tt>, or <tt>-u <key-id></tt> is passed, the command\r
creates a <em>tag</em> object, and requires the tag message. Unless\r
-<tt>-m <msg></tt> is given, an editor is started for the user to type\r
+<tt>-m <msg></tt> or <tt>-F <file></tt> is given, an editor is started for the user to type\r
in the tag message.</p>\r
<p>Otherwise just the SHA1 object name of the commit object is\r
written (i.e. a lightweight tag).</p>\r
</dt>\r
<dd>\r
<p>\r
- Verify the gpg signature of given the tag\r
+ Verify the gpg signature of the given tag names.\r
</p>\r
</dd>\r
<dt>\r
<num> specifies how many lines from the annotation, if any,\r
are printed when using -l.\r
The default is not to print any annotation lines.\r
+ If no number is given to <tt>-n</tt>, only the first line is printed.\r
</p>\r
</dd>\r
<dt>\r
<dd>\r
<p>\r
List tags with names that match the given pattern (or all if no pattern is given).\r
+ Typing "git tag" without arguments, also lists all tags.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:57 UTC\r
+Last updated 11-Aug-2007 08:29:16 UTC\r
</div>\r
</div>\r
</body>\r
'git-tag' [-a | -s | -u <key-id>] [-f] [-m <msg> | -F <file>] <name> [<head>]
'git-tag' -d <name>...
'git-tag' [-n [<num>]] -l [<pattern>]
-'git-tag' -v <name>
+'git-tag' -v <name>...
DESCRIPTION
-----------
If one of `-a`, `-s`, or `-u <key-id>` is passed, the command
creates a 'tag' object, and requires the tag message. Unless
-`-m <msg>` is given, an editor is started for the user to type
+`-m <msg>` or `-F <file>` is given, an editor is started for the user to type
in the tag message.
Otherwise just the SHA1 object name of the commit object is
Delete existing tags with the given names.
-v::
- Verify the gpg signature of given the tag
+ Verify the gpg signature of the given tag names.
-n <num>::
<num> specifies how many lines from the annotation, if any,
are printed when using -l.
The default is not to print any annotation lines.
+ If no number is given to `-n`, only the first line is printed.
-l <pattern>::
List tags with names that match the given pattern (or all if no pattern is given).
+ Typing "git tag" without arguments, also lists all tags.
-m <msg>::
Use the given tag message (instead of prompting)
<h2>NAME</h2>\r
<div class="sectionbody">\r
<p>git-verify-tag -\r
- Check the GPG signature of tag\r
+ Check the GPG signature of tags\r
</p>\r
</div>\r
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-verify-tag</em> <tag></p>\r
+<p><em>git-verify-tag</em> <tag>…</p>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:59 UTC\r
+Last updated 11-Aug-2007 08:29:16 UTC\r
</div>\r
</div>\r
</body>\r
NAME
----
-git-verify-tag - Check the GPG signature of tag
+git-verify-tag - Check the GPG signature of tags
SYNOPSIS
--------
-'git-verify-tag' <tag>
+'git-verify-tag' <tag>...
DESCRIPTION
-----------
<p>Manipulators:</p>\r
<dl>\r
<dt>\r
+<a href="git-config.html">git-config(1)</a>\r
+</dt>\r
+<dd>\r
+<p>\r
+ Get and set repository or global options.\r
+</p>\r
+</dd>\r
+<dt>\r
<a href="git-convert-objects.html">git-convert-objects(1)</a>\r
</dt>\r
<dd>\r
</p>\r
</dd>\r
<dt>\r
-<a href="git-repack.html">git-repack(1)</a>\r
-</dt>\r
-<dd>\r
-<p>\r
- Pack unpacked objects in a repository.\r
-</p>\r
-</dd>\r
-<dt>\r
-<a href="git-config.html">git-config(1)</a>\r
+<a href="git-remote.html">git-remote(1)</a>\r
</dt>\r
<dd>\r
<p>\r
- Get and set repository or global options.\r
+ manage set of tracked repositories.\r
</p>\r
</dd>\r
<dt>\r
-<a href="git-remote.html">git-remote(1)</a>\r
+<a href="git-repack.html">git-repack(1)</a>\r
</dt>\r
<dd>\r
<p>\r
- manage set of tracked repositories.\r
+ Pack unpacked objects in a repository.\r
</p>\r
</dd>\r
</dl>\r
</dt>\r
<dd>\r
<p>\r
- Check the GPG signature of tag.\r
+ Check the GPG signature of tags.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 06-Aug-2007 04:38:49 UTC\r
+Last updated 11-Aug-2007 08:29:16 UTC\r
</div>\r
</div>\r
</body>\r
- ssh://{startsb}user@{endsb}host.xz/~/path/to/repo.git
===============================================================
-SSH is the default transport protocol. You can optionally specify
-which user to log-in as, and an alternate, scp-like syntax is also
-supported. Both syntaxes support username expansion,
-as does the native git protocol. The following three are
-identical to the last three above, respectively:
+SSH is the default transport protocol over the network. You can
+optionally specify which user to log-in as, and an alternate,
+scp-like syntax is also supported. Both syntaxes support
+username expansion, as does the native git protocol. The following
+three are identical to the last three above, respectively:
===============================================================
- {startsb}user@{endsb}host.xz:/path/to/repo.git/
- {startsb}user@{endsb}host.xz:path/to/repo.git
===============================================================
-To sync with a local directory, use:
+To sync with a local directory, you can use:
===============================================================
- /path/to/repo.git/
+- file:///path/to/repo.git/
===============================================================
+
+They are mostly equivalent, except when cloning. See
+gitlink:git-clone[1] for details.
projects / git.git / commitdiff