On Thu, Oct 18, 2012 at 03:54:29AM -0400, Jeff King wrote: > On Thu, Oct 18, 2012 at 09:49:04AM +0200, Johannes Sixt wrote: > > > > - s/.*/GIT_'$uid'_NAME='\''&'\''; export GIT_'$uid'_NAME/p > > > > Didn't you lose the export GIT_$uid_{NAME,EMAIL,DATE} parts somewhere on > > the way? > > Yikes, you're right. I didn't even notice, as the test suite still > passes. I can see how the env filter would still be able to see the > variables, but the commit-tree call wouldn't. I guess it happens to work > because we do not test alternate idents in our filter branch tests (IOW, > we are silently rewriting each commit during the filter-branch, but it > happens to have the same identities).
Hrm. We _do_ test this in t7003. Weirder, if I instrument filter-branch like this: diff --git a/git-filter-branch.sh b/git-filter-branch.sh index 69406ae..1b504ce 100755 --- a/git-filter-branch.sh +++ b/git-filter-branch.sh @@ -298,8 +298,13 @@ while read commit parents; do git cat-file commit "$commit" >../commit || die "Cannot read commit $commit" + echo >&2 pre: $GIT_AUTHOR_NAME + sh -c 'echo >&2 pre, subshell: $GIT_AUTHOR_NAME' + eval "$(set_ident <../commit)" || die "setting author/committer failed for commit $commit" + echo >&2 post: $GIT_AUTHOR_NAME + sh -c 'echo >&2 post, subshell: $GIT_AUTHOR_NAME' eval "$filter_env" < /dev/null || die "env filter failed: $filter_env" diff --git a/t/t7003-filter-branch.sh b/t/t7003-filter-branch.sh index 4d13e10..ce57fc5 100755 --- a/t/t7003-filter-branch.sh +++ b/t/t7003-filter-branch.sh @@ -174,6 +174,8 @@ test_expect_success 'author information is preserved' ' test 1 = $(git rev-list --author="B V Uips" preserved-author | wc -l) ' +test_done + test_expect_success "remove a certain author's commits" ' echo i > i && test_tick && and run t7003, it shows that the variable is properly exported to the sub-process! But I can't seem to figure out why. Confused... -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html