branch.autosetupmerge::
Tells `git-branch` and `git-checkout` to setup new branches
- so that linkgit:git-pull[1] will appropriately merge from that
- remote branch. Note that even if this option is not set,
+ so that linkgit:git-pull[1] will appropriately merge from the
+ starting point branch. Note that even if this option is not set,
this behavior can be chosen per-branch using the `--track`
- and `--no-track` options. This option defaults to true.
+ and `--no-track` options. The valid settings are: `false` -- no
+ automatic setup is done; `true` -- automatic setup is done when the
+ starting point is a remote branch; `always` -- automatic setup is
+ done when the starting point is either a local branch or remote
+ branch. This option defaults to true.
branch.<name>.remote::
When in branch <name>, it tells `git fetch` which remote to fetch.
warning. This is meant to reduce packing time on multiprocessor
machines. The required amount of memory for the delta search window
is however multiplied by the number of threads.
+ Specifying 0 will cause git to auto-detect the number of CPU's
+ and set the number of threads accordingly.
pack.indexVersion::
Specify the default pack index version. Valid values are 1 for
archiving user's umask will be used instead. See umask(2) and
linkgit:git-archive[1].
+url.<base>.insteadOf::
+ Any URL that starts with this value will be rewritten to
+ start, instead, with <base>. In cases where some site serves a
+ large number of repositories, and serves them with multiple
+ access methods, and some users need to use different access
+ methods, this feature allows people to specify any of the
+ equivalent URLs and have git automatically rewrite the URL to
+ the best alternative for the particular user, even for a
+ never-before-seen repository on the site. When more than one
+ insteadOf strings match a given URL, the longest match is used.
+
user.email::
Your email address to be recorded in any newly created commits.
Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and
Swap two inputs; that is, show differences from index or
on-disk file to tree contents.
+--relative[=<path>]::
+ When run from a subdirectory of the project, it can be
+ told to exclude changes outside the directory and show
+ pathnames relative to it with this option. When you are
+ not in a subdirectory (e.g. in a bare repository), you
+ can name which subdirectory to make the output relative
+ to by giving a <path> as an argument.
+
--text::
Treat all files as text.
working tree to it; use "git checkout <newbranch>" to switch to the\r
new branch.</p>\r
<p>When a local branch is started off a remote branch, git sets up the\r
-branch so that <a href="git-pull.html">git-pull(1)</a> will appropriately merge from that\r
-remote branch. If this behavior is not desired, it is possible to\r
-disable it using the global <tt>branch.autosetupmerge</tt> configuration\r
-flag. That setting can be overridden by using the <tt>--track</tt>\r
-and <tt>--no-track</tt> options.</p>\r
+branch so that <a href="git-pull.html">git-pull(1)</a> will appropriately merge from\r
+the remote branch. This behavior may be changed via the global\r
+<tt>branch.autosetupmerge</tt> configuration flag. That setting can be\r
+overridden by using the <tt>--track</tt> and <tt>--no-track</tt> options.</p>\r
<p>With a <em>-m</em> or <em>-M</em> option, <oldbranch> will be renamed to <newbranch>.\r
If <oldbranch> had a corresponding reflog, it is renamed to match\r
<newbranch>, and a reflog entry is created to remember the branch\r
</dt>\r
<dd>\r
<p>\r
- Set up configuration so that git-pull will automatically\r
- retrieve data from the remote branch. Use this if you always\r
- pull from the same remote branch into the new branch, or if you\r
- don't want to use "git pull <repository> <refspec>" explicitly.\r
- This behavior is the default. Set the\r
- branch.autosetupmerge configuration variable to false if you\r
- want git-checkout and git-branch to always behave as if\r
- <em>--no-track</em> were given.\r
+ When creating a new branch, set up configuration so that git-pull\r
+ will automatically retrieve data from the start point, which must be\r
+ a branch. Use this if you always pull from the same upstream branch\r
+ into the new branch, and if you don't want to use "git pull\r
+ <repository> <refspec>" explicitly. This behavior is the default\r
+ when the start point is a remote branch. Set the\r
+ branch.autosetupmerge configuration variable to <tt>false</tt> if you want\r
+ git-checkout and git-branch to always behave as if <em>--no-track</em> were\r
+ given. Set it to <tt>always</tt> if you want this behavior when the\r
+ start-point is either a local or remote branch.\r
</p>\r
</dd>\r
<dt>\r
</dt>\r
<dd>\r
<p>\r
- When a branch is created off a remote branch,\r
- set up configuration so that git-pull will not retrieve data\r
- from the remote branch, ignoring the branch.autosetupmerge\r
- configuration variable.\r
+ Ignore the branch.autosetupmerge configuration variable.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 12-Feb-2008 03:18:04 UTC\r
+Last updated 28-Feb-2008 00:25:37 UTC\r
</div>\r
</div>\r
</body>\r
new branch.
When a local branch is started off a remote branch, git sets up the
-branch so that linkgit:git-pull[1] will appropriately merge from that
-remote branch. If this behavior is not desired, it is possible to
-disable it using the global `branch.autosetupmerge` configuration
-flag. That setting can be overridden by using the `--track`
-and `--no-track` options.
+branch so that linkgit:git-pull[1] will appropriately merge from
+the remote branch. This behavior may be changed via the global
+`branch.autosetupmerge` configuration flag. That setting can be
+overridden by using the `--track` and `--no-track` options.
With a '-m' or '-M' option, <oldbranch> will be renamed to <newbranch>.
If <oldbranch> had a corresponding reflog, it is renamed to match
Display the full sha1s in output listing rather than abbreviating them.
--track::
- Set up configuration so that git-pull will automatically
- retrieve data from the remote branch. Use this if you always
- pull from the same remote branch into the new branch, or if you
- don't want to use "git pull <repository> <refspec>" explicitly.
- This behavior is the default. Set the
- branch.autosetupmerge configuration variable to false if you
- want git-checkout and git-branch to always behave as if
- '--no-track' were given.
+ When creating a new branch, set up configuration so that git-pull
+ will automatically retrieve data from the start point, which must be
+ a branch. Use this if you always pull from the same upstream branch
+ into the new branch, and if you don't want to use "git pull
+ <repository> <refspec>" explicitly. This behavior is the default
+ when the start point is a remote branch. Set the
+ branch.autosetupmerge configuration variable to `false` if you want
+ git-checkout and git-branch to always behave as if '--no-track' were
+ given. Set it to `always` if you want this behavior when the
+ start-point is either a local or remote branch.
--no-track::
- When a branch is created off a remote branch,
- set up configuration so that git-pull will not retrieve data
- from the remote branch, ignoring the branch.autosetupmerge
- configuration variable.
+ Ignore the branch.autosetupmerge configuration variable.
<branchname>::
The name of the branch to create or delete.
</dt>\r
<dd>\r
<p>\r
- When -b is given and a branch is created off a remote branch,\r
- set up configuration so that git-pull will automatically\r
- retrieve data from the remote branch. Use this if you always\r
- pull from the same remote branch into the new branch, or if you\r
- don't want to use "git pull <repository> <refspec>" explicitly.\r
- This behavior is the default. Set the\r
- branch.autosetupmerge configuration variable to false if you\r
- want git-checkout and git-branch to always behave as if\r
- <em>--no-track</em> were given.\r
+ When creating a new branch, set up configuration so that git-pull\r
+ will automatically retrieve data from the start point, which must be\r
+ a branch. Use this if you always pull from the same upstream branch\r
+ into the new branch, and if you don't want to use "git pull\r
+ <repository> <refspec>" explicitly. This behavior is the default\r
+ when the start point is a remote branch. Set the\r
+ branch.autosetupmerge configuration variable to <tt>false</tt> if you want\r
+ git-checkout and git-branch to always behave as if <em>--no-track</em> were\r
+ given. Set it to <tt>always</tt> if you want this behavior when the\r
+ start-point is either a local or remote branch.\r
</p>\r
</dd>\r
<dt>\r
</dt>\r
<dd>\r
<p>\r
- When -b is given and a branch is created off a remote branch,\r
- set up configuration so that git-pull will not retrieve data\r
- from the remote branch, ignoring the branch.autosetupmerge\r
- configuration variable.\r
+ Ignore the branch.autosetupmerge configuration variable.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 12-Feb-2008 03:18:04 UTC\r
+Last updated 28-Feb-2008 00:25:37 UTC\r
</div>\r
</div>\r
</body>\r
may restrict the characters allowed in a branch name.
--track::
- When -b is given and a branch is created off a remote branch,
- set up configuration so that git-pull will automatically
- retrieve data from the remote branch. Use this if you always
- pull from the same remote branch into the new branch, or if you
- don't want to use "git pull <repository> <refspec>" explicitly.
- This behavior is the default. Set the
- branch.autosetupmerge configuration variable to false if you
- want git-checkout and git-branch to always behave as if
- '--no-track' were given.
+ When creating a new branch, set up configuration so that git-pull
+ will automatically retrieve data from the start point, which must be
+ a branch. Use this if you always pull from the same upstream branch
+ into the new branch, and if you don't want to use "git pull
+ <repository> <refspec>" explicitly. This behavior is the default
+ when the start point is a remote branch. Set the
+ branch.autosetupmerge configuration variable to `false` if you want
+ git-checkout and git-branch to always behave as if '--no-track' were
+ given. Set it to `always` if you want this behavior when the
+ start-point is either a local or remote branch.
--no-track::
- When -b is given and a branch is created off a remote branch,
- set up configuration so that git-pull will not retrieve data
- from the remote branch, ignoring the branch.autosetupmerge
- configuration variable.
+ Ignore the branch.autosetupmerge configuration variable.
-l::
Create the new branch's reflog. This activates recording of
</ul>\r
</div></div>\r
<p>They are equivalent, except the former implies --local option.</p>\r
+<p>If there are a large number of similarly-named remote repositories and\r
+you want to use a different format for them (such that the URLs you\r
+use will be rewritten into URLs that work), you can create a\r
+configuration section of the form:</p>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt> [url "<actual url base>"]\r
+ insteadOf = <other url base></tt></pre>\r
+</div></div>\r
+<p>For example, with this:</p>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt> [url "git://git.host.xz/"]\r
+ insteadOf = host.xz:/path/to/\r
+ insteadOf = work:</tt></pre>\r
+</div></div>\r
+<p>a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be\r
+rewritten in any context that takes a URL to be "git://git.host.xz/repo.git".</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 14-Feb-2008 00:51:07 UTC\r
+Last updated 28-Feb-2008 00:25:37 UTC\r
</div>\r
</div>\r
</body>\r
<dd>\r
<p>\r
Tells <tt>git-branch</tt> and <tt>git-checkout</tt> to setup new branches\r
- so that <a href="git-pull.html">git-pull(1)</a> will appropriately merge from that\r
- remote branch. Note that even if this option is not set,\r
+ so that <a href="git-pull.html">git-pull(1)</a> will appropriately merge from the\r
+ starting point branch. Note that even if this option is not set,\r
this behavior can be chosen per-branch using the <tt>--track</tt>\r
- and <tt>--no-track</tt> options. This option defaults to true.\r
+ and <tt>--no-track</tt> options. The valid settings are: <tt>false</tt> — no\r
+ automatic setup is done; <tt>true</tt> — automatic setup is done when the\r
+ starting point is a remote branch; <tt>always</tt> — automatic setup is\r
+ done when the starting point is either a local branch or remote\r
+ branch. This option defaults to true.\r
</p>\r
</dd>\r
<dt>\r
warning. This is meant to reduce packing time on multiprocessor\r
machines. The required amount of memory for the delta search window\r
is however multiplied by the number of threads.\r
+ Specifying 0 will cause git to auto-detect the number of CPU's\r
+ and set the number of threads accordingly.\r
</p>\r
</dd>\r
<dt>\r
</p>\r
</dd>\r
<dt>\r
+url.<base>.insteadOf\r
+</dt>\r
+<dd>\r
+<p>\r
+ Any URL that starts with this value will be rewritten to\r
+ start, instead, with <base>. In cases where some site serves a\r
+ large number of repositories, and serves them with multiple\r
+ access methods, and some users need to use different access\r
+ methods, this feature allows people to specify any of the\r
+ equivalent URLs and have git automatically rewrite the URL to\r
+ the best alternative for the particular user, even for a\r
+ never-before-seen repository on the site. When more than one\r
+ insteadOf strings match a given URL, the longest match is used.\r
+</p>\r
+</dd>\r
+<dt>\r
user.email\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 25-Feb-2008 08:40:21 UTC\r
+Last updated 28-Feb-2008 00:25:38 UTC\r
</div>\r
</div>\r
</body>\r
candidates to describe the input committish consider\r
up to <n> candidates. Increasing <n> above 10 will take\r
slightly longer but may produce a more accurate result.\r
+ An <n> of 0 will cause only exact matches to be output.\r
+</p>\r
+</dd>\r
+<dt>\r
+--exact-match\r
+</dt>\r
+<dd>\r
+<p>\r
+ Only output exact matches (a tag directly references the\r
+ supplied commit). This is a synonym for --candidates=0.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 12-Feb-2008 03:18:05 UTC\r
+Last updated 28-Feb-2008 00:25:38 UTC\r
</div>\r
</div>\r
</body>\r
candidates to describe the input committish consider
up to <n> candidates. Increasing <n> above 10 will take
slightly longer but may produce a more accurate result.
+ An <n> of 0 will cause only exact matches to be output.
+
+--exact-match::
+ Only output exact matches (a tag directly references the
+ supplied commit). This is a synonym for --candidates=0.
--debug::
Verbosely display information about the searching strategy
</p>\r
</dd>\r
<dt>\r
+--relative[=<path>]\r
+</dt>\r
+<dd>\r
+<p>\r
+ When run from a subdirectory of the project, it can be\r
+ told to exclude changes outside the directory and show\r
+ pathnames relative to it with this option. When you are\r
+ not in a subdirectory (e.g. in a bare repository), you\r
+ can name which subdirectory to make the output relative\r
+ to by giving a <path> as an argument.\r
+</p>\r
+</dd>\r
+<dt>\r
--text\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jan-2008 07:50:13 UTC\r
+Last updated 28-Feb-2008 00:25:38 UTC\r
</div>\r
</div>\r
</body>\r
</p>\r
</dd>\r
<dt>\r
+--relative[=<path>]\r
+</dt>\r
+<dd>\r
+<p>\r
+ When run from a subdirectory of the project, it can be\r
+ told to exclude changes outside the directory and show\r
+ pathnames relative to it with this option. When you are\r
+ not in a subdirectory (e.g. in a bare repository), you\r
+ can name which subdirectory to make the output relative\r
+ to by giving a <path> as an argument.\r
+</p>\r
+</dd>\r
+<dt>\r
--text\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jan-2008 07:50:13 UTC\r
+Last updated 28-Feb-2008 00:25:39 UTC\r
</div>\r
</div>\r
</body>\r
</p>\r
</dd>\r
<dt>\r
+--relative[=<path>]\r
+</dt>\r
+<dd>\r
+<p>\r
+ When run from a subdirectory of the project, it can be\r
+ told to exclude changes outside the directory and show\r
+ pathnames relative to it with this option. When you are\r
+ not in a subdirectory (e.g. in a bare repository), you\r
+ can name which subdirectory to make the output relative\r
+ to by giving a <path> as an argument.\r
+</p>\r
+</dd>\r
+<dt>\r
--text\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jan-2008 07:50:15 UTC\r
+Last updated 28-Feb-2008 00:25:39 UTC\r
</div>\r
</div>\r
</body>\r
</p>\r
</dd>\r
<dt>\r
+--relative[=<path>]\r
+</dt>\r
+<dd>\r
+<p>\r
+ When run from a subdirectory of the project, it can be\r
+ told to exclude changes outside the directory and show\r
+ pathnames relative to it with this option. When you are\r
+ not in a subdirectory (e.g. in a bare repository), you\r
+ can name which subdirectory to make the output relative\r
+ to by giving a <path> as an argument.\r
+</p>\r
+</dd>\r
+<dt>\r
--text\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jan-2008 07:50:15 UTC\r
+Last updated 28-Feb-2008 00:25:41 UTC\r
</div>\r
</div>\r
</body>\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
+<p>If there are a large number of similarly-named remote repositories and\r
+you want to use a different format for them (such that the URLs you\r
+use will be rewritten into URLs that work), you can create a\r
+configuration section of the form:</p>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt> [url "<actual url base>"]\r
+ insteadOf = <other url base></tt></pre>\r
+</div></div>\r
+<p>For example, with this:</p>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt> [url "git://git.host.xz/"]\r
+ insteadOf = host.xz:/path/to/\r
+ insteadOf = work:</tt></pre>\r
+</div></div>\r
+<p>a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be\r
+rewritten in any context that takes a URL to be "git://git.host.xz/repo.git".</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 27-Jan-2008 08:23:28 UTC\r
+Last updated 28-Feb-2008 00:25:41 UTC\r
</div>\r
</div>\r
</body>\r
[--in-reply-to=Message-Id] [--suffix=.<sfx>]\r
[--ignore-if-in-upstream]\r
[--subject-prefix=Subject-Prefix]\r
+ [--cc=<email>]\r
+ [--cover-letter]\r
[ <since> | <revision range> ]</div></div>\r
</div>\r
<h2>DESCRIPTION</h2>\r
</p>\r
</dd>\r
<dt>\r
+--relative[=<path>]\r
+</dt>\r
+<dd>\r
+<p>\r
+ When run from a subdirectory of the project, it can be\r
+ told to exclude changes outside the directory and show\r
+ pathnames relative to it with this option. When you are\r
+ not in a subdirectory (e.g. in a bare repository), you\r
+ can name which subdirectory to make the output relative\r
+ to by giving a <path> as an argument.\r
+</p>\r
+</dd>\r
+<dt>\r
--text\r
</dt>\r
<dd>\r
</p>\r
</dd>\r
<dt>\r
+--cc=<email>\r
+</dt>\r
+<dd>\r
+<p>\r
+ Add a "Cc:" header to the email headers. This is in addition\r
+ to any configured headers, and may be used multiple times.\r
+</p>\r
+</dd>\r
+<dt>\r
+--cover-letter\r
+</dt>\r
+<dd>\r
+<p>\r
+ Generate a cover letter template. You still have to fill in\r
+ a description, but the shortlog and the diffstat will be\r
+ generated for you.\r
+</p>\r
+</dd>\r
+<dt>\r
--suffix=.<sfx>\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jan-2008 07:50:21 UTC\r
+Last updated 28-Feb-2008 00:25:42 UTC\r
</div>\r
</div>\r
</body>\r
--------
[verse]
'git-format-patch' [-k] [-o <dir> | --stdout] [--thread]
- [--attach[=<boundary>] | --inline[=<boundary>]]
- [-s | --signoff] [<common diff options>]
- [-n | --numbered | -N | --no-numbered]
- [--start-number <n>] [--numbered-files]
- [--in-reply-to=Message-Id] [--suffix=.<sfx>]
- [--ignore-if-in-upstream]
- [--subject-prefix=Subject-Prefix]
+ [--attach[=<boundary>] | --inline[=<boundary>]]
+ [-s | --signoff] [<common diff options>]
+ [-n | --numbered | -N | --no-numbered]
+ [--start-number <n>] [--numbered-files]
+ [--in-reply-to=Message-Id] [--suffix=.<sfx>]
+ [--ignore-if-in-upstream]
+ [--subject-prefix=Subject-Prefix]
+ [--cc=<email>]
+ [--cover-letter]
[ <since> | <revision range> ]
DESCRIPTION
allows for useful naming of a patch series, and can be
combined with the --numbered option.
+--cc=<email>::
+ Add a "Cc:" header to the email headers. This is in addition
+ to any configured headers, and may be used multiple times.
+
+--cover-letter::
+ Generate a cover letter template. You still have to fill in
+ a description, but the shortlog and the diffstat will be
+ generated for you.
+
--suffix=.<sfx>::
Instead of using `.patch` as the suffix for generated
filenames, use specified suffix. A common alternative is
</p>\r
</dd>\r
<dt>\r
+--relative[=<path>]\r
+</dt>\r
+<dd>\r
+<p>\r
+ When run from a subdirectory of the project, it can be\r
+ told to exclude changes outside the directory and show\r
+ pathnames relative to it with this option. When you are\r
+ not in a subdirectory (e.g. in a bare repository), you\r
+ can name which subdirectory to make the output relative\r
+ to by giving a <path> as an argument.\r
+</p>\r
+</dd>\r
+<dt>\r
--text\r
</dt>\r
<dd>\r
</p>\r
</dd>\r
<dt>\r
+-F, --fixed-strings\r
+</dt>\r
+<dd>\r
+<p>\r
+ Consider the limiting patterns to be fixed strings (don't interpret\r
+ pattern as a regular expression).\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 19-Jan-2008 08:01:34 UTC\r
+Last updated 28-Feb-2008 00:25:42 UTC\r
</div>\r
</div>\r
</body>\r
This is meant to reduce packing time on multiprocessor machines.\r
The required amount of memory for the delta search window is\r
however multiplied by the number of threads.\r
+ Specifying 0 will cause git to auto-detect the number of CPU's\r
+ and set the number of threads accordingly.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 10-Feb-2008 10:47:42 UTC\r
+Last updated 28-Feb-2008 00:25:42 UTC\r
</div>\r
</div>\r
</body>\r
This is meant to reduce packing time on multiprocessor machines.
The required amount of memory for the delta search window is
however multiplied by the number of threads.
+ Specifying 0 will cause git to auto-detect the number of CPU's
+ and set the number of threads accordingly.
--index-version=<version>[,<offset>]::
This is intended to be used by the test suite only. It allows
</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
+<p>If there are a large number of similarly-named remote repositories and\r
+you want to use a different format for them (such that the URLs you\r
+use will be rewritten into URLs that work), you can create a\r
+configuration section of the form:</p>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt> [url "<actual url base>"]\r
+ insteadOf = <other url base></tt></pre>\r
+</div></div>\r
+<p>For example, with this:</p>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt> [url "git://git.host.xz/"]\r
+ insteadOf = host.xz:/path/to/\r
+ insteadOf = work:</tt></pre>\r
+</div></div>\r
+<p>a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be\r
+rewritten in any context that takes a URL to be "git://git.host.xz/repo.git".</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 20-Feb-2008 10:44:09 UTC\r
+Last updated 28-Feb-2008 00:25:43 UTC\r
</div>\r
</div>\r
</body>\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
+<p>If there are a large number of similarly-named remote repositories and\r
+you want to use a different format for them (such that the URLs you\r
+use will be rewritten into URLs that work), you can create a\r
+configuration section of the form:</p>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt> [url "<actual url base>"]\r
+ insteadOf = <other url base></tt></pre>\r
+</div></div>\r
+<p>For example, with this:</p>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt> [url "git://git.host.xz/"]\r
+ insteadOf = host.xz:/path/to/\r
+ insteadOf = work:</tt></pre>\r
+</div></div>\r
+<p>a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be\r
+rewritten in any context that takes a URL to be "git://git.host.xz/repo.git".</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 20-Feb-2008 10:44:09 UTC\r
+Last updated 28-Feb-2008 00:25:43 UTC\r
</div>\r
</div>\r
</body>\r
[ --(author|committer|grep)=<pattern> ]\r
[ --regexp-ignore-case | \-i ]\r
[ --extended-regexp | \-E ]\r
+ [ --fixed-strings | \-F ]\r
[ --date={local|relative|default|iso|rfc|short} ]\r
[ [--objects | --objects-edge] [ --unpacked ] ]\r
[ --pretty | --header ]\r
</p>\r
</dd>\r
<dt>\r
+-F, --fixed-strings\r
+</dt>\r
+<dd>\r
+<p>\r
+ Consider the limiting patterns to be fixed strings (don't interpret\r
+ pattern as a regular expression).\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 19-Jan-2008 08:01:34 UTC\r
+Last updated 28-Feb-2008 00:25:44 UTC\r
</div>\r
</div>\r
</body>\r
[ \--(author|committer|grep)=<pattern> ]
[ \--regexp-ignore-case | \-i ]
[ \--extended-regexp | \-E ]
+ [ \--fixed-strings | \-F ]
[ \--date={local|relative|default|iso|rfc|short} ]
[ [\--objects | \--objects-edge] [ \--unpacked ] ]
[ \--pretty | \--header ]
</p>\r
</dd>\r
</dl>\r
+<div class="admonitionblock">\r
+<table><tr>\r
+<td class="icon">\r
+<div class="title">Note</div>\r
+</td>\r
+<td class="content">SVN itself only stores times in UTC and nothing else. The regular svn\r
+client converts the UTC time to the local time (or based on the TZ=\r
+environment). This command has the same behaviour.</td>\r
+</tr></table>\r
+</div>\r
<p>Any other arguments are passed directly to `git log'</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 12-Feb-2008 03:18:07 UTC\r
+Last updated 28-Feb-2008 00:25:44 UTC\r
</div>\r
</div>\r
</body>\r
our version of --pretty=oneline
--
+
+NOTE: SVN itself only stores times in UTC and nothing else. The regular svn
+client converts the UTC time to the local time (or based on the TZ=
+environment). This command has the same behaviour.
++
Any other arguments are passed directly to `git log'
'blame'::
Consider the limiting patterns to be extended regular expressions
instead of the default basic regular expressions.
+-F, --fixed-strings::
+
+ Consider the limiting patterns to be fixed strings (don't interpret
+ pattern as a regular expression).
+
--remove-empty::
Stop when a given path disappears from the tree.
ifdef::git-clone[]
They are equivalent, except the former implies --local option.
endif::git-clone[]
+
+
+If there are a large number of similarly-named remote repositories and
+you want to use a different format for them (such that the URLs you
+use will be rewritten into URLs that work), you can create a
+configuration section of the form:
+
+------------
+ [url "<actual url base>"]
+ insteadOf = <other url base>
+------------
+
+For example, with this:
+
+------------
+ [url "git://git.host.xz/"]
+ insteadOf = host.xz:/path/to/
+ insteadOf = work:
+------------
+
+a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be
+rewritten in any context that takes a URL to be "git://git.host.xz/repo.git".
+
My Various Git Projects / git.git / commitdiff