.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-BLAME" "1" "06/08/2007" "Git 1.5.2.rc0.95.ga0715" "Git Manual"
+.TH "GIT\-BLAME" "1" "06/13/2007" "Git 1.5.2.1.271.g90ac" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.SH "SYNOPSIS"
.sp
.nf
-\fIgit\-blame\fR [\-c] [\-b] [\-\-root] [\-s] [\-l] [\-t] [\-f] [\-n] [\-p] [\-\-incremental] [\-L n,m]
+\fIgit\-blame\fR [\-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>
.fi
.TP
\-s
Suppress author name and timestamp from the output.
+.TP
+\-w
+Ignore whitespace when comparing parent's version and child's to find where the lines came from.
.SH "THE PORCELAIN FORMAT"
In this format, each line is output after a header; the header at the minimum has the first line which has:
.TP 3
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-CVSIMPORT" "1" "06/08/2007" "Git 1.5.2.1.144.gabc40" "Git Manual"
+.TH "GIT\-CVSIMPORT" "1" "06/13/2007" "Git 1.5.2.1.271.g90ac" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
[\-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>]
.fi
.SH "DESCRIPTION"
Imports a CVS repository into git. It will either create a new repository, or incrementally import into an existing one.
Splitting the CVS log into patch sets is done by \fIcvsps\fR. At least version 2.1 is required.
-You should \fBnever\fR do any work of your own on the branches that are created by git\-cvsimport. The 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 \fIgit merge\fR incremental imports, or any CVS branches, yourself.
+You should \fBnever\fR do any work of your own on the branches that are 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 \fIgit merge\fR incremental imports, or any CVS branches, yourself. It is advisable to specify a named remote via \-r to separate and protect the incoming branches.
.SH "OPTIONS"
.TP
\-v
\-C <target\-dir>
The git repository to import to. If the directory doesn't exist, it will be created. Default is the current directory.
.TP
+\-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.
+.TP
\-o <branch\-for\-HEAD>
-The \fIHEAD\fR branch from CVS is imported to the \fIorigin\fR branch within the git repository, as \fIHEAD\fR 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 \fIHEAD\fR branch from CVS is imported to the \fIorigin\fR branch within the git repository, as \fIHEAD\fR already has a special meaning for git. When a remote is specified the \fIHEAD\fR branch is named remotes/<remote>/master mirroring git\-clone behaviour. Use this option if you want to import into a different branch.
Use \fI\-o master\fR for continuing an import that was initially done by the old cvs2git tool.
.TP