Martin Langhoff wrote: > On 5/18/07, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: >> If you have a solution for that problem, please enlighten me: I don't. > > Ok - worst case scenario - have a minimal hints file that tells me the > ranges to fetch all commits and all trees. To reduce that Add to the > hints file data to name the hashes (or even better - offsets) for the > delta chains that contain commits+trees relevant to all the heads - > minus 10, 20, 30, 40 commits and 1,2,4,8 and 16 days. > > So there's a good chance the client can get the commits+trees needed > efficiently. For blobs, all you need is the index to mark the delta > chains you need. By the way, I think we always should get the whole delta chain, unless we are absolutely sure that we have base object(s) in repo. -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - 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
