[PATCH 1/2] fix filter-branch documentation
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Oct 17, 2007, 02:22 UTC
- Message-ID
- <Pine.LNX.4.64.0710170322000.25221@racer.site>
- In-Reply-To
- <18197.24051.863751.436705@lisa.zopyra.com>
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> --- Documentation/git-filter-branch.txt | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt index c878ed3..ba9b4fb 100644 --- a/Documentation/git-filter-branch.txt +++ b/Documentation/git-filter-branch.txt @@ -180,8 +180,7 @@ A significantly faster version: git filter-branch --index-filter 'git update-index --remove filename' HEAD -------------------------------------------------------------------------- -Now, you will get the rewritten history saved in the branch 'newbranch' -(your current branch is left untouched). +Now, you will get the rewritten history saved in HEAD. To set a commit (which typically is at the tip of another history) to be the parent of the current initial commit, in
-- 1.5.3.4.1223.ga973c