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>
Johannes Schindelin committed
Oct 17, 2007 at 03:22 UTC
8ef44519a64d3ac863a9a3a6dbdba09ea275c822
1 file changed
+1
-2
Documentation/git-filter-branch.txt
+1
-2
@@ -180,8 +180,7 @@ A significantly faster version:
180
git filter-branch --index-filter 'git update-index --remove filename' HEAD
181
--------------------------------------------------------------------------
182
183
-Now, you will get the rewritten history saved in the branch 'newbranch'
184
-(your current branch is left untouched).
183
+Now, you will get the rewritten history saved in HEAD.
184
185
To set a commit (which typically is at the tip of another
186
history) to be the parent of the current initial commit, in