On Wed, Mar 25, 2009 at 6:57 PM, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > Hi, > > On Wed, 25 Mar 2009, Thomas Koch wrote: > >> we host a public GIT repository on our high availability company >> cluster. Cloning the repo causes a trafic volume of 326 MB. We'd like to >> avoid that much trafic while still leaving the GIT repo where it is. >> >> I could imagine the following conversation between the GIT client and >> server: >> >> Client: Wanna clone! >> Server: You're welcome. Please note, that while I serve the most current >> state, you can get objects much faster from my collegue Server >> CHEAPHOST. >> Client: Thank you. Will take all the objects I can get from CHEAPHOST >> and come back if I should need anything else! >> >> The enduser should not need to specify anything, but only the regular >> git clone EXPENSIVEHOST line. >> >> Your thoughts? > > That sounds a lot like the mirror-sync idea. > > Ciao, > Dscho > -- > 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 > Yea, that would definitely fall under mirror-sync functionality. I wrote up my GSoC proposal for implementing this to the list (http://marc.info/?l=git&m=123795365411979&w=2), comments and criticism welcome. Andrew -- 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
