<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
<div class="verseblock">\r
-<div class="content"><em>git-blame</em> [-c] [-b] [--root] [-s] [-l] [-t] [-f] [-n] [-p] [--incremental] [-L n,m]\r
+<div class="content"><em>git-blame</em> [-c] [-b] [-l] [--root] [-t] [-f] [-n] [-s] [-p] [-w] [--incremental] [-L n,m]\r
[-S <revs-file>] [-M] [-C] [-C] [--since=<date>]\r
[<rev> | --contents <file>] [--] <file></div></div>\r
</div>\r
Suppress author name and timestamp from the output.\r
</p>\r
</dd>\r
+<dt>\r
+-w\r
+</dt>\r
+<dd>\r
+<p>\r
+ Ignore whitespace when comparing parent's version and\r
+ child's to find where the lines came from.\r
+</p>\r
+</dd>\r
</dl>\r
</div>\r
<h2>THE PORCELAIN FORMAT</h2>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 08-Jun-2007 16:08:01 UTC\r
+Last updated 13-Jun-2007 08:29:16 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
[verse]
-'git-blame' [-c] [-b] [--root] [-s] [-l] [-t] [-f] [-n] [-p] [--incremental] [-L n,m]
+'git-blame' [-c] [-b] [-l] [--root] [-t] [-f] [-n] [-s] [-p] [-w] [--incremental] [-L n,m]
[-S <revs-file>] [-M] [-C] [-C] [--since=<date>]
[<rev> | --contents <file>] [--] <file>
-s::
Suppress author name and timestamp from the output.
+-w::
+ Ignore whitespace when comparing parent's version and
+ child's to find where the lines came from.
+
+
THE PORCELAIN FORMAT
--------------------
[-A <author-conv-file>] [-p <options-for-cvsps>] [-P <file>]\r
[-C <git_repository>] [-z <fuzz>] [-i] [-k] [-u] [-s <subst>]\r
[-a] [-m] [-M <regex>] [-S <regex>] [-L <commitlimit>]\r
- [<CVS_module>]</div></div>\r
+ [-r <remote>] [<CVS_module>]</div></div>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
<p>Splitting the CVS log into patch sets is done by <em>cvsps</em>.\r
At least version 2.1 is required.</p>\r
<p>You should <strong>never</strong> do any work of your own on the branches that are\r
-created by git-cvsimport. The initial import will create and populate a\r
+created by git-cvsimport. By default initial import will create and populate a\r
"master" branch from the CVS repository's main branch which you're free\r
to work with; after that, you need to <em>git merge</em> incremental imports, or\r
-any CVS branches, yourself.</p>\r
+any CVS branches, yourself. It is advisable to specify a named remote via\r
+-r to separate and protect the incoming branches.</p>\r
</div>\r
<h2>OPTIONS</h2>\r
<div class="sectionbody">\r
</p>\r
</dd>\r
<dt>\r
+-r <remote>\r
+</dt>\r
+<dd>\r
+<p>\r
+ The git remote to import this CVS repository into.\r
+ Moves all CVS branches into remotes/<remote>/<branch>\r
+ akin to the git-clone --use-separate-remote option.\r
+</p>\r
+</dd>\r
+<dt>\r
-o <branch-for-HEAD>\r
</dt>\r
<dd>\r
<p>\r
- The <em>HEAD</em> branch from CVS is imported to the <em>origin</em> branch within\r
- the git repository, as <em>HEAD</em> already has a special meaning for git.\r
- Use this option if you want to import into a different branch.\r
+ When no remote is specified (via -r) the <em>HEAD</em> branch\r
+ from CVS is imported to the <em>origin</em> branch within the git\r
+ repository, as <em>HEAD</em> already has a special meaning for git.\r
+ When a remote is specified the <em>HEAD</em> branch is named\r
+ remotes/<remote>/master mirroring git-clone behaviour.\r
+ Use this option if you want to import into a different\r
+ branch.\r
</p>\r
<p>Use <em>-o master</em> for continuing an import that was initially done by\r
the old cvs2git tool.</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 08-Jun-2007 16:08:06 UTC\r
+Last updated 13-Jun-2007 08:29:16 UTC\r
</div>\r
</div>\r
</body>\r
[-A <author-conv-file>] [-p <options-for-cvsps>] [-P <file>]
[-C <git_repository>] [-z <fuzz>] [-i] [-k] [-u] [-s <subst>]
[-a] [-m] [-M <regex>] [-S <regex>] [-L <commitlimit>]
- [<CVS_module>]
+ [-r <remote>] [<CVS_module>]
DESCRIPTION
At least version 2.1 is required.
You should *never* do any work of your own on the branches that are
-created by git-cvsimport. The initial import will create and populate a
+created by git-cvsimport. By default initial import will create and populate a
"master" branch from the CVS repository's main branch which you're free
to work with; after that, you need to 'git merge' incremental imports, or
-any CVS branches, yourself.
+any CVS branches, yourself. It is advisable to specify a named remote via
+-r to separate and protect the incoming branches.
+
OPTIONS
-------
The git repository to import to. If the directory doesn't
exist, it will be created. Default is the current directory.
+-r <remote>::
+ The git remote to import this CVS repository into.
+ Moves all CVS branches into remotes/<remote>/<branch>
+ akin to the git-clone --use-separate-remote option.
+
-o <branch-for-HEAD>::
- The 'HEAD' branch from CVS is imported to the 'origin' branch within
- the git repository, as 'HEAD' already has a special meaning for git.
- Use this option if you want to import into a different branch.
+ When no remote is specified (via -r) the 'HEAD' branch
+ from CVS is imported to the 'origin' branch within the git
+ repository, as 'HEAD' already has a special meaning for git.
+ When a remote is specified the 'HEAD' branch is named
+ remotes/<remote>/master mirroring git-clone behaviour.
+ Use this option if you want to import into a different
+ branch.
+
Use '-o master' for continuing an import that was initially done by
the old cvs2git tool.