On 8/26/07, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > > Doesn't kernel.org use alternates or something equivalent for serving > > up all those nearly identical kernel trees? > > Absolutely. And that's the point. "git-daemon" will serve a nice > individualized pack, even though any particular repository doesn't have > one, but is really a combination of "the base Linus pack + extensions". A really simple change to the git protocol would be to make the client loop on the request. On the first request the server would see that the client has no objects and send the "base Linus pack". The client would then loop around and repeat the process which will trigger the current pack building process. Do pack files contain enough information about the heads of the object chains for this to work? The client needs to be able to determine it's state after receiving the pack and send the info back in the next round. I'm not buying the security argument. If you want something kept hidden get it out of the public db. If I know the sha of the hidden object can't I just add a head for it and git-deamon will happily send it and the chain up to it to me? -- Jon Smirl jonsmirl@xxxxxxxxx - 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
