From: "Benjamin R. Haskell" <zsh@benizi.com>
To: Zsh Workers <zsh-workers@zsh.org>
Subject: Re: SourceForge CVS down for the weekend, it looks like
Date: Sat, 27 Mar 2010 15:07:21 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.01.1003271436210.19615@hp.internal> (raw)
In-Reply-To: <733654e31003271118k1b33cb7fx9ec5de3d7249fa96@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1158 bytes --]
On Sat, 27 Mar 2010, Wayne Davison wrote:
> On Sat, Mar 27, 2010 at 9:53 AM, Benjamin R. Haskell <zsh@benizi.com> wrote:
> if the SF git server were to go down, how is it any different
> than the SF CVS server going down?
>
>
> There are multiple git servers, all of which share the load for
> serving every git request, no matter the project. CVS doesn't play
> well with shared storage,
For anyone else interested in specifics, googling CVS NFS comes up with
this thread[1], but more interesting was Linus's explanation of how git
avoids NFS problems[2]. (NFS being the natural search term when
"doesn't play well" and "shared storage" are mentioned.)
> so there is just one cvs server for a particular project that is
> active at any one time. This means that there are outages for
> maintenance, outages for fail-overs, etc., more-so than there'd be
> with git.
Thanks for the explanation. Makes sense now.
--
Best,
Ben
[1] CVS and NFS - ~4.5 years old - http://mongers.org/cvs#cvs_nfs
[2] what's the current wisdom on git over NFS/CIFS? - 2009-07-02 -
http://permalink.gmane.org/gmane.comp.version-control.git/122670
next prev parent reply other threads:[~2010-03-27 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-27 3:34 Bart Schaefer
2010-03-27 16:02 ` Wayne Davison
2010-03-27 16:53 ` Benjamin R. Haskell
2010-03-27 18:18 ` Wayne Davison
2010-03-27 19:07 ` Benjamin R. Haskell [this message]
2010-03-27 18:45 ` Peter Stephenson
2010-03-27 19:33 ` Clint Adams
2010-03-28 1:47 ` Wayne Davison
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=alpine.LNX.2.01.1003271436210.19615@hp.internal \
--to=zsh@benizi.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).