From: Jon Seymour <jon.seymour@gmail.com>
To: George Spelvin <linux@horizon.com>
Cc: git@vger.kernel.org, spearce@spearce.org
Subject: Re: is hosting a read-mostly git repo on a distributed file system practical?
Date: Wed, 13 Apr 2011 14:57:10 +1000 [thread overview]
Message-ID: <BANLkTi=cE4=EC0C4MA5iac6_O-YMsW_SLg@mail.gmail.com> (raw)
In-Reply-To: <20110413034715.15553.qmail@science.horizon.com>
On Wed, Apr 13, 2011 at 1:47 PM, George Spelvin <linux@horizon.com> wrote:
> I think the answers are yes, but I have to make a vouple of things clear:
> * You can *definitely* control repack behaviour. .keep files are the
> simplest way to prevent repacking.
Good.
> * Are you talking about hosting only a "bare" repository, or one with
> the unpacked source tree as well? If you try to run git commands on
> a large network-mounted source tree, things can get more than a bit
> sluggish; git recursively stats the whole tree fairly frequently.
> (There are ways to precent that, notably core.ignoreStat, but they
> make it less friendly.)
Bare. Developers use local disk for local repos and working tree.
> * You can clone from a repository mounted on the file system just as
> easily as you can from a network server. So there's no need to set
> up a server if you find it onconvenient.
Are there advantages to using rsync for the initial clone? Will I get
better restartability in the case that the network is less than 100% reliable?
I do remember trying to use a DFS-file system in the past, before I understood
pack management properly and I seem to recall issues with network reliability.
> Indeed, you could easily do everything via DFS. Give everyone a personal
> "public" repo to push to, which is read-only to everyone else, and let
> the integrator pull from those.
>
I'll probably use ssh-secured peer to peer for publishing purposes.
The main thing I want
the DFS-hosted repo for is to provide a single, always up, go-to point
for the shared tag set.
>
> Anyway, I hope this helps!
>
Yep, thank you.
jon.
next prev parent reply other threads:[~2011-04-13 4:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 3:47 is hosting a read-mostly git repo on a distributed file system practical? George Spelvin
2011-04-13 4:57 ` Jon Seymour [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-13 1:40 Jon Seymour
2011-04-13 2:06 ` Shawn Pearce
2011-04-13 2:29 ` 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='BANLkTi=cE4=EC0C4MA5iac6_O-YMsW_SLg@mail.gmail.com' \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
--cc=linux@horizon.com \
--cc=spearce@spearce.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).