From f80888ce6d55ea765cec661d4586575afc0e64ba Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Fri, 14 Sep 2007 10:06:48 +0000 Subject: [PATCH] Autogenerated HTML docs for v1.5.3.1-56-g611d --- git-filter-branch.html | 6 +----- git-filter-branch.txt | 5 ----- 2 files changed, 1 insertion(+), 10 deletions(-) diff --git a/git-filter-branch.html b/git-filter-branch.html index 84ed10364..0a2d811c5 100644 --- a/git-filter-branch.html +++ b/git-filter-branch.html @@ -524,10 +524,6 @@ git filter-branch $graft-id..HEAD git commit-tree "$@"; fi' HEAD -

Note that the changes introduced by the commits, and not reverted by -subsequent commits, will still be in the rewritten branch. If you want -to throw out _changes_ together with the commits, you should use the -interactive mode of git-rebase(1).

The function skip_commits is defined as follows:

@@ -598,7 +594,7 @@ and the git list <git@vger.kernel.org>

diff --git a/git-filter-branch.txt b/git-filter-branch.txt index 29bb8cec0..c878ed395 100644 --- a/git-filter-branch.txt +++ b/git-filter-branch.txt @@ -220,11 +220,6 @@ git filter-branch --commit-filter ' fi' HEAD ------------------------------------------------------------------------------ -Note that the changes introduced by the commits, and not reverted by -subsequent commits, will still be in the rewritten branch. If you want -to throw out _changes_ together with the commits, you should use the -interactive mode of gitlink:git-rebase[1]. - The function 'skip_commits' is defined as follows: -------------------------- -- 2.26.2