summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: f70dda2)
raw | patch | inline | side by side (parent: f70dda2)
author | Kevin Ballard <kevin@sb.org> | |
Fri, 30 May 2008 21:43:40 +0000 (14:43 -0700) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Tue, 3 Jun 2008 03:36:09 +0000 (20:36 -0700) |
The old description was misleading and logically impossible. It claimed that
the ancestors of the original commit would be re-written to have the multiple
emitted ids as parents. Not only would this modify existing objects, but it
would create a cycle. What this actually does is pass the multiple emitted ids
to the newly-created children to use as parents.
Signed-off-by: Kevin Ballard <kevin@sb.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
the ancestors of the original commit would be re-written to have the multiple
emitted ids as parents. Not only would this modify existing objects, but it
would create a cycle. What this actually does is pass the multiple emitted ids
to the newly-created children to use as parents.
Signed-off-by: Kevin Ballard <kevin@sb.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-filter-branch.txt | patch | blob | history |
index 506c37af7021e2e16caab5ffe72bca9bc2f28927..35cb1677f770f13065905df2cb3cddcda5b63ca2 100644 (file)
stdin. The commit id is expected on stdout.
+
As a special extension, the commit filter may emit multiple
-commit ids; in that case, ancestors of the original commit will
+commit ids; in that case, the rewritten children of the original commit will
have all of them as parents.
+
You can use the 'map' convenience function in this filter, and other