From: linux@horizon.com
To: git@vger.kernel.org
Subject: Is there such a thing as a git:// proxy?
Date: 18 Jun 2006 08:42:50 -0400 [thread overview]
Message-ID: <20060618124250.15471.qmail@science.horizon.com> (raw)
I have several machines tracking kernel.org, and I've been moving away
from downloading patch files periodically (cached very nicely by squid)
to just doing "git pull".
But it seems silly to be sucking four copies of the same data from
kernel.org.
Now, one obvious solution is to have one master copy track kernel.org
and have all the other local machines track that. But then I have to
manually pull the local master every time.
Has anyone put together something that can automatically check
upstream for updates when someone fetches from it?
Ultimately desirable features would, I suppose include:
- Pulling over ssh as well (using auth agent forwarding to pull
from upstream)
- Support for arbitrary projects (so the cache server can handle
"git clone" requests), if I develop a desire to pull an -mm or
-libata-dev or whatever kernel, it will also work.
- Using a single shared object pool for the above.
- Cache cleanup if a project hasn't been used in long enough.
(You'd probably just time out the heads and let git-prune get
rid of the objects.)
- Recycling the pack from the upstream server rather than regenerating it.
- Progress reporting on the upstream fetch (since the point is that
the upstream server pipe is narrower).
- Transparent proxy support
... but I'll settle for the simple solution to start. Perhaps it could
be as simple as a pre-upload hook invoked by git-upload-pack?
This hasn't gotten itchy enough for me to start scratching it myself,
but I figured I'd mention it and see if anyone was interested.
next reply other threads:[~2006-06-18 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 12:42 linux [this message]
2006-06-18 17:02 ` Is there such a thing as a git:// proxy? Linus Torvalds
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=20060618124250.15471.qmail@science.horizon.com \
--to=linux@horizon.com \
--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).