fix filter-branch documentation
The man page for filter-branch still talked about writing the result to the branch "newbranch". This is hopefully the last place where the old behaviour was described. Noticed by Bill Lear. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
This commit is contained in:

committed by
Shawn O. Pearce

parent
7e23b06d59
commit
8ef44519a6
@ -180,8 +180,7 @@ A significantly faster version:
|
|||||||
git filter-branch --index-filter 'git update-index --remove filename' HEAD
|
git filter-branch --index-filter 'git update-index --remove filename' HEAD
|
||||||
--------------------------------------------------------------------------
|
--------------------------------------------------------------------------
|
||||||
|
|
||||||
Now, you will get the rewritten history saved in the branch 'newbranch'
|
Now, you will get the rewritten history saved in HEAD.
|
||||||
(your current branch is left untouched).
|
|
||||||
|
|
||||||
To set a commit (which typically is at the tip of another
|
To set a commit (which typically is at the tip of another
|
||||||
history) to be the parent of the current initial commit, in
|
history) to be the parent of the current initial commit, in
|
||||||
|
Reference in New Issue
Block a user