From: Andrew Wang <azuriel@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Thomas Koch <thomas@koch.ro>, git@vger.kernel.org
Subject: Re: Use alternate GIT servers to share traffic
Date: Thu, 26 Mar 2009 00:30:18 -0400 [thread overview]
Message-ID: <1c7233eb0903252130q190245cavfe077749504f277@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0903252356160.26370@intel-tinevez-2-302>
On Wed, Mar 25, 2009 at 6:57 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> 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@vger.kernel.org
> 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
next prev parent reply other threads:[~2009-03-26 4:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 20:45 Use alternate GIT servers to share traffic Thomas Koch
2009-03-25 22:57 ` Johannes Schindelin
2009-03-26 4:30 ` Andrew Wang [this message]
2009-03-26 13:40 ` Samuel Lucas Vaz de Mello
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1c7233eb0903252130q190245cavfe077749504f277@mail.gmail.com \
--to=azuriel@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=thomas@koch.ro \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).