Hi Ed, Thank you for your advice. I have few knowledge about git. Ed W: > I *think* what you would do in this case (just for reference), is to > create a new empty repo, then you would fetch locally just the branches > you cared about from the original repo, then remove the remote repo.
Remove the remote repo? Bruno (the administrator of remote git tree) had made a new tree named aufs2-2.6-test.git which contains linux kernel but aufs2. Is it equivalent to your idea? > It's possible you then need to cleanup the remote data in your .git > directory (not sure), but I believe this can also be achieved most > simply by just recloning this new repo to a fresh directory, however I > believe the remotes are just a subdirectory in your .git? Unfortunately I don't know what 'the remote data' is. > Alternatively you could create a new bare repo, then *push* just the > branches you want to export to the new repo. Run a repack and a gc on > the new repo On the remote side? If so, how about running git fsck, gc or something to current aufs2-2.6.git on the remote side? > Finally, assuming you have local access, have you tried a "git gc" on > the broken data? I don't have shell access to the public git tree. I have git-fsck to my local tree and it reports many 'daggling' entries. Is this a problem? > I have never seen a broken git repo before, so I'm actually a little > curious to hear how this works out? (In contrast, svn seems to have That is what I am most concerning now. Without finding out the cause, the problem may appear again in the future, I am afraid. J. R. Okajima ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference
