From: Thomas Koch <thomas@koch.ro>
To: git@vger.kernel.org
Subject: Use alternate GIT servers to share traffic
Date: Wed, 25 Mar 2009 21:45:29 +0100 [thread overview]
Message-ID: <200903252145.30226.thomas@koch.ro> (raw)
Hi,
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?
Best regards,
--
Thomas Koch, http://www.koch.ro
YMC AG, http://www.ymc.ch
next reply other threads:[~2009-03-25 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 20:45 Thomas Koch [this message]
2009-03-25 22:57 ` Use alternate GIT servers to share traffic Johannes Schindelin
2009-03-26 4:30 ` Andrew Wang
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=200903252145.30226.thomas@koch.ro \
--to=thomas@koch.ro \
--cc=git@vger.kernel.org \
/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).