On Tue, Dec 3, 2013 at 2:17 PM, Junio C Hamano <gits...@pobox.com> wrote: > Duy Nguyen <pclo...@gmail.com> writes: > >>> If nothing else has happened in the repository, perhaps, but I >>> suspect that the real problem is how you would prove it. For >>> example, I am guessing that your Scenario 4 could be something like: >>> >>> : setup #1 >>> $ git repack -a -d -f >>> $ git prune >>> >>> : scenario #4 >>> $ git commit --allow-empty -m 'new commit' >>> >>> which would add a single loose object to the repository, advancing >>> the current branch ref by one commit, fast-forwarding relative to >>> the state you were in after setup #1. >>> >>> But how would you efficiently prove that it was the only thing that >>> happened? >> >> Shawn mentioned elsewhere that we could generate bundle header in and >> keep it in pack-XXX.bh file at pack creation time. With that >> information we could verify if a ref has been reset, just fast >> forwarded or even deleted. > > With what information? If you keep the back-then-current information > and nothing else, how would you differentiate between the simple > scenario #4 above vs 'lost and new' two commit versions of the > scenario? The endpoints should both show that one ref (and only one > ref) advanced by one commit, but one has cruft in the object > database while the other does not.
Yeah I was wrong. Reading Martin's mail again I wonder how we just "grab all objects and skip history traversal". Who will decide object order in the new pack if we don't traverse history and collect path information. -- Duy -- 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