On 1/5/07, Junio C Hamano <junkio@xxxxxxx> wrote:
> Using git-verify-pack from master does not fail. It actually does > verify the pack (after a pretty decent wait.) I should have tried > master first before sending out the first mail. :) Depends on which "master" -- I pushed out the "chuncked hashing" fix on "master" as commit 8977c110 as part of the update last night.
Well, that would definitely explain it. :) I did a fresh 'git pull' on master last night before I ran the git-verify-pack, and that was around 11PM PST.
> Junio: Did you still want me to try those steps with that patch > anyway, even though it works on master? It would give us a confirmation that the above actually fixes the problem, if your 1.4.1 fails to verify that same new pack you just generated, on which you saw that the "master" (assuming you mean the one with the above patch) works correctly. If your "master" before 8977c110 already passes, then there is something else going on, which would be worrysome.
The 'master' I had definitely included 8977c110. I can try it out with the tip from before that commit, though, if you want. Also, 'git-prune' took about 30 minutes to run to completion. Oddly, git-prune didn't remove the older packs - does git-prune ignore packs? 'git-repack -a -d' did remove them. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html