Hi Jonathan,
This bug appears to be fixed as of Git 1.8.1.5, the newest upstream
release. When I repeat your reproduction recipe, the 'clone' succeeds
with no error message, and tagFoo exists in the cloned repo.
-- 8< --
mkdir foo &&
(
cd foo &&
git init &&
echo A >foo.txt &&
git add foo.txt &&
git commit -m "Created foo" &&
git tag -am "Tagging foo" tagFoo &&
git filter-branch --env-filter 'export GIT_AUTHOR_NAME=xyz123'
\
--tag-name-filter cat -- --all
) &&
git clone file:///`pwd`/foo newFoo &&
git --git-dir=foo/.git for-each-ref &&
git --git-dir=newFoo/.git for-each-ref
->
...
dd70efcfeca8e5dae5d7fc1e1dcc404ee55bbaf8 commit refs/heads/master
cf9a6f8cfa2e71cca3860e4d20a0ae2b0cb1097e commit refs/original/refs/heads/master
cf9a6f8cfa2e71cca3860e4d20a0ae2b0cb1097e commit refs/original/refs/tags/tagFoo
79d6acee511138d732dffec280f2c2e0b2200b99 tag refs/tags/tagFoo
dd70efcfeca8e5dae5d7fc1e1dcc404ee55bbaf8 commit refs/heads/master
dd70efcfeca8e5dae5d7fc1e1dcc404ee55bbaf8 commit refs/remotes/origin/HEAD
dd70efcfeca8e5dae5d7fc1e1dcc404ee55bbaf8 commit refs/remotes/origin/master
79d6acee511138d732dffec280f2c2e0b2200b99 tag refs/tags/tagFoo
-- >8 --
You've suggested a couple of times on the git-list that you would be
happy for the BTS to be used as a bugtracker for Git itself, if I
understand you correctly. That'd certainly be a much-needed facility
for the Git project. How would you suggest recording here the fact
that this bug has been resolved in Git 1.8.1.5?
(The bug may also be already fixed in squeeze's 1.7.2.5 or wheezy's
1.7.10.4; I don't know. That would probably simplify recording the
resolution here, but I'm also interested in the general case.)
Thanks!
Greg
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
