.\" 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" "01/28/2007" "" ""
+.TH "GIT\-BLAME" "1" "02/06/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.sp
.nf
\fIgit\-blame\fR [\-c] [\-l] [\-t] [\-f] [\-n] [\-p] [\-\-incremental] [\-L n,m] [\-S <revs\-file>]
- [\-M] [\-C] [\-C] [\-\-since=<date>] [<rev>] [\-\-] <file>
+ [\-M] [\-C] [\-C] [\-\-since=<date>] [<rev> | \-\-contents <file>] [\-\-] <file>
.fi
.SH "DESCRIPTION"
Annotates each line in the given file with information from the revision which last modified the line. Optionally, start annotating from the given revision.
\-\-incremental
Show the result incrementally in a format designed for machine consumption.
.TP
+\-\-contents <file>
+When <rev> is not specified, the command annotates the changes starting backwards from the working tree copy. This flag makes the command pretend as if the working tree copy has the contents of he named file (specify \- to make the command read from the standard input).
+.TP
\-M
Detect moving lines in the file as well. When a commit moves a block of lines in a file (e.g. the original file has A and then B, and the commit changes it to B and then A), traditional \fIblame\fR algorithm typically blames the lines that were moved up (i.e. B) to the parent and 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.
.TP
.\" 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\-CVSEXPORTCOMMIT" "1" "01/19/2007" "" ""
+.TH "GIT\-CVSEXPORTCOMMIT" "1" "02/06/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.SH "NAME"
git\-cvsexportcommit \- Export a single commit to a CVS checkout
.SH "SYNOPSIS"
-\fIgit\-cvsexportcommit\fR [\-h] [\-v] [\-c] [\-p] [\-a] [\-f] [\-m msgprefix] [PARENTCOMMIT] COMMITID
+\fIgit\-cvsexportcommit\fR [\-h] [\-v] [\-c] [\-P] [\-p] [\-a] [\-f] [\-m msgprefix] [PARENTCOMMIT] COMMITID
.SH "DESCRIPTION"
Exports a commit from GIT to a CVS checkout, making it easier to merge patches from a git repository into a CVS repository.
\-f
Force the merge even if the files are not up to date.
.TP
+\-P
+Force the parent commit, even if it is not a direct parent.
+.TP
\-m
Prepend the commit message with the provided prefix. Useful for patch series and the like.
.TP
.\" 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\-FOR\-EACH\-REF" "1" "01/29/2007" "" ""
+.TH "GIT\-FOR\-EACH\-REF" "1" "02/06/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
For all objects, the following names can be used:
.TP
refname
-The name of the ref (the part after $GIT_DIR/refs/).
+The name of the ref (the part after $GIT_DIR/).
.TP
objecttype
The type of the object (blob, tree, commit, tag).
.\" 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\-REBASE" "1" "01/19/2007" "" ""
+.TH "GIT\-REBASE" "1" "02/06/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.fi
This is useful when topicB does not depend on topicA.
+A range of commits could also be removed with rebase. If we have the following situation:
+.sp
+.nf
+ E\-\-\-F\-\-\-G\-\-\-H\-\-\-I\-\-\-J topicA
+.fi
+then the command
+.sp
+.nf
+git\-rebase \-\-onto topicA~5 topicA~2 topicA
+.fi
+would result in the removal of commits F and G:
+.sp
+.nf
+ E\-\-\-H'\-\-\-I'\-\-\-J' topicA
+.fi
+This is useful if F and G were flawed in some way, or should not be part of topicA. Note that the argument to \-\-onto and the <upstream> parameter can be any valid commit\-ish.
+
In case of conflict, git\-rebase will stop at the first problematic commit and leave conflict markers in the tree. You can use git diff to locate the markers (<<<<<<) and make edits to resolve the conflict. For each file you edit, you need to tell git that the conflict has been resolved, typically this would be done with
.sp
.nf
.SH "OPTIONS"
.TP
<newbase>
-Starting point at which to create the new commits. If the \-\-onto option is not specified, the starting point is <upstream>.
+Starting point at which to create the new commits. If the \-\-onto option is not specified, the starting point is <upstream>. May be any valid commit, and not just an existing branch name.
.TP
<upstream>
-Upstream branch to compare against.
+Upstream branch to compare against. May be any valid commit, not just an existing branch name.
.TP
<branch>
Working branch; defaults to HEAD.
.\" 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" "7" "02/05/2007" "" ""
+.TH "GIT" "7" "02/06/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)