From: Jon Seymour <jon.seymour@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: is hosting a read-mostly git repo on a distributed file system practical?
Date: Wed, 13 Apr 2011 11:40:06 +1000 [thread overview]
Message-ID: <BANLkTiniGcRAHbt5LP2NVhE+c8grOr5sLA@mail.gmail.com> (raw)
Is it practical to host a read-mostly git repo on a WAN-based
distributed file system?
The idea is that most developers would use the DFS-based repo to track
the tip of the development stream, but only the integrator would
publish updates to the DFS-based repo.
As such, the need to repack the DFS-based repo will be somewhat, but
not completely, reduced.
Is this going to be practical, or are whole of repo operations
eventually going to kill me because of latency and bandwidth issues
associated with use of the DFS?
Are there things I can do with the git configuration (such as limiting
repacking behaviour) that will help?
jon.
next reply other threads:[~2011-04-13 1:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 1:40 Jon Seymour [this message]
2011-04-13 2:06 ` is hosting a read-mostly git repo on a distributed file system practical? Shawn Pearce
2011-04-13 2:29 ` Jon Seymour
-- strict thread matches above, loose matches on Subject: below --
2011-04-13 3:47 George Spelvin
2011-04-13 4:57 ` Jon Seymour
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=BANLkTiniGcRAHbt5LP2NVhE+c8grOr5sLA@mail.gmail.com \
--to=jon.seymour@gmail.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).