<div class="verseblock">\r
<div class="content"><em>git-clone</em> [--template=<template_directory>] [-l [-s]] [-q] [-n] [--bare]\r
[-o <name>] [-u <upload-pack>] [--reference <repository>]\r
- [--use-separate-remote | --no-separate-remote] <repository>\r
- [<directory>]</div></div>\r
+ <repository> [<directory>]</div></div>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
</p>\r
</dd>\r
<dt>\r
---use-separate-remote\r
-</dt>\r
-<dd>\r
-<p>\r
- Save remotes heads under <tt>$GIT_DIR/refs/remotes/origin/</tt> instead\r
- of <tt>$GIT_DIR/refs/heads/</tt>. Only the local master branch is\r
- saved in the latter. This is the default.\r
-</p>\r
-</dd>\r
-<dt>\r
---no-separate-remote\r
-</dt>\r
-<dd>\r
-<p>\r
- Save remotes heads in the same namespace as the local\r
- heads, `$GIT_DIR/refs/heads/'. In regular repositories,\r
- this is a legacy setup git-clone created by default in\r
- older Git versions, and will be removed before the next\r
- major release.\r
-</p>\r
-</dd>\r
-<dt>\r
<repository>\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 16-Dec-2006 22:16:25 UTC\r
+Last updated 21-Dec-2006 02:25:49 UTC\r
</div>\r
</div>\r
</body>\r
[verse]
'git-clone' [--template=<template_directory>] [-l [-s]] [-q] [-n] [--bare]
[-o <name>] [-u <upload-pack>] [--reference <repository>]
- [--use-separate-remote | --no-separate-remote] <repository>
- [<directory>]
+ <repository> [<directory>]
DESCRIPTION
-----------
if unset the templates are taken from the installation
defined default, typically `/usr/share/git-core/templates`.
---use-separate-remote::
- Save remotes heads under `$GIT_DIR/refs/remotes/origin/` instead
- of `$GIT_DIR/refs/heads/`. Only the local master branch is
- saved in the latter. This is the default.
-
---no-separate-remote::
- Save remotes heads in the same namespace as the local
- heads, `$GIT_DIR/refs/heads/'. In regular repositories,
- this is a legacy setup git-clone created by default in
- older Git versions, and will be removed before the next
- major release.
-
<repository>::
The (possibly remote) repository to clone from. It can
be any URL git-fetch supports.
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-diff</em> [ --diff-options ] <tree-ish>{0,2} [--] [<path>…]</p>\r
+<p><em>git-diff</em> [ --diff-options ] <commit>{0,2} [--] [<path>…]</p>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
<dd>\r
<p>\r
This form is to view the changes you staged for the next\r
- commit relative to the named <tree-ish>. Typically you\r
+ commit relative to the named <commit>. Typically you\r
would want comparison with the latest commit, so if you\r
do not give <commit>, it defaults to HEAD.\r
</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 16-Dec-2006 07:43:51 UTC\r
+Last updated 21-Dec-2006 02:25:50 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
-'git-diff' [ --diff-options ] <
tree-ish>{0,2} [--] [<path>...]
+'git-diff' [ --diff-options ] <
commit>{0,2} [--] [<path>...]
DESCRIPTION
-----------
'git-diff' [--options] --cached [<commit>] [--] [<path>...]::
This form is to view the changes you staged for the next
- commit relative to the named <tree-ish>. Typically you
+ commit relative to the named <commit>. Typically you
would want comparison with the latest commit, so if you
do not give <commit>, it defaults to HEAD.
against the latest changes in the SVN repository.\r
An optional command-line argument may be specified as an\r
alternative to HEAD.\r
- This is advantageous over <em>commit</em> (below) because it produces\r
+ This is advantageous over <em>set-tree</em> (below) because it produces\r
cleaner, more linear history.\r
</p>\r
</dd>\r
</div></div>\r
</dd>\r
<dt>\r
-<em>commit</em>\r
+<em>set-tree</em>\r
</dt>\r
<dd>\r
<p>\r
</dt>\r
<dd>\r
<p>\r
-Only used with the <em>commit</em> command.\r
+Only used with the <em>set-tree</em> command.\r
</p>\r
<p>Read a list of commits from stdin and commit them in reverse\r
order. Only the leading sha1 is read from each line, so\r
</dt>\r
<dd>\r
<p>\r
-Only used with the <em>dcommit</em>, <em>commit</em> and <em>commit-diff</em> commands.\r
+Only used with the <em>dcommit</em>, <em>set-tree</em> and <em>commit-diff</em> commands.\r
</p>\r
<p>Remove directories from the SVN tree if there are no files left\r
behind. SVN can version empty directories, and they are not\r
</dt>\r
<dd>\r
<p>\r
-Only used with the <em>dcommit</em>, <em>commit</em> and <em>commit-diff</em> commands.\r
+Only used with the <em>dcommit</em>, <em>set-tree</em> and <em>commit-diff</em> commands.\r
</p>\r
<p>Edit the commit message before committing to SVN. This is off by\r
default for objects that are commits, and forced on when committing\r
</dt>\r
<dd>\r
<p>\r
-Only used with the <em>dcommit</em>, <em>commit</em> and <em>commit-diff</em> commands.\r
+Only used with the <em>dcommit</em>, <em>set-tree</em> and <em>commit-diff</em> commands.\r
</p>\r
<p>They are both passed directly to git-diff-tree see\r
<a href="git-diff-tree.html">git-diff-tree(1)</a> for more information.</p>\r
</dt>\r
<dd>\r
<p>\r
-Used with <em>fetch</em>, <em>dcommit</em> or <em>commit</em>.\r
+Used with <em>fetch</em>, <em>dcommit</em> or <em>set-tree</em>.\r
</p>\r
<p>This can be used to join arbitrary git branches to remotes/git-svn\r
on new commits where the tree object is equivalent.</p>\r
<h2>REBASE VS. PULL</h2>\r
<div class="sectionbody">\r
<p>Originally, git-svn recommended that the remotes/git-svn branch be\r
-pulled from. This is because the author favored <em>git-svn commit B</em>\r
-to commit a single head rather than the <em>git-svn commit A..B</em> notation\r
+pulled from. This is because the author favored <em>git-svn set-tree B</em>\r
+to commit a single head rather than the <em>git-svn set-tree A..B</em> notation\r
to commit multiple commits.</p>\r
-<p>If you use <em>git-svn commit A..B</em> to commit several diffs and you do not\r
+<p>If you use <em>git-svn set-tree A..B</em> to commit several diffs and you do not\r
have the latest remotes/git-svn merged into my-branch, you should use\r
<em>git rebase</em> to update your work branch instead of <em>git pull</em>. <em>pull</em>\r
can cause non-linear history to be flattened when committing into SVN,\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 13-Dec-2006 06:35:40 UTC\r
+Last updated 21-Dec-2006 02:25:50 UTC\r
</div>\r
</div>\r
</body>\r
against the latest changes in the SVN repository.
An optional command-line argument may be specified as an
alternative to HEAD.
- This is advantageous over 'commit' (below) because it produces
+ This is advantageous over 'set-tree' (below) because it produces
cleaner, more linear history.
'log'::
Any other arguments are passed directly to `git log'
-'commit'::
+'set-tree'::
You should consider using 'dcommit' instead of this command.
Commit specified commit or tree objects to SVN. This relies on
your imported fetch data being up-to-date. This makes
-::
--stdin::
-Only used with the 'commit' command.
+Only used with the 'set-tree' command.
Read a list of commits from stdin and commit them in reverse
order. Only the leading sha1 is read from each line, so
--rmdir::
-Only used with the 'dcommit', 'commit' and 'commit-diff' commands.
+Only used with the 'dcommit', 'set-tree' and 'commit-diff' commands.
Remove directories from the SVN tree if there are no files left
behind. SVN can version empty directories, and they are not
-e::
--edit::
-Only used with the 'dcommit', 'commit' and 'commit-diff' commands.
+Only used with the 'dcommit', 'set-tree' and 'commit-diff' commands.
Edit the commit message before committing to SVN. This is off by
default for objects that are commits, and forced on when committing
-l<num>::
--find-copies-harder::
-Only used with the 'dcommit', 'commit' and 'commit-diff' commands.
+Only used with the 'dcommit', 'set-tree' and 'commit-diff' commands.
They are both passed directly to git-diff-tree see
gitlink:git-diff-tree[1] for more information.
-b<refname>::
--branch <refname>::
-Used with 'fetch', 'dcommit' or 'commit'.
+Used with 'fetch', 'dcommit' or 'set-tree'.
This can be used to join arbitrary git branches to remotes/git-svn
on new commits where the tree object is equivalent.
---------------
Originally, git-svn recommended that the remotes/git-svn branch be
-pulled from. This is because the author favored 'git-svn commit B'
-to commit a single head rather than the 'git-svn commit A..B' notation
+pulled from. This is because the author favored 'git-svn set-tree B'
+to commit a single head rather than the 'git-svn set-tree A..B' notation
to commit multiple commits.
-If you use 'git-svn commit A..B' to commit several diffs and you do not
+If you use 'git-svn set-tree A..B' to commit several diffs and you do not
have the latest remotes/git-svn merged into my-branch, you should use
'git rebase' to update your work branch instead of 'git pull'. 'pull'
can cause non-linear history to be flattened when committing into SVN,
projects / git.git / commitdiff