On 2/11/07, Shawn O. Pearce <spearce@xxxxxxxxxxx> wrote:
Jon Smirl <jonsmirl@xxxxxxxxx> wrote: > Is this happening because the repository on the server is not > completely packed? It is basically building a pack of the whole thing > and shipping it to me, right? Correct. The wire protocol only allows us to send one pack. So we have to pack everything and transmit it as a single unit. > If that is the case, why not first pack the whole repository and then > copy it down the wire? Now the next clone that comes along doesn't > have to do so much work. Would this help to eliminate some of the load > at kernel.org? Probably, but then the daemon needs write access to the repository. This isn't required right now; it can be strictly read-only and still serve the contents.
Does it need write access for push to work, can the server check for write access and save the complete repack if it has access? This appears to be causing a lot of needless work for kernel.org. -- 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