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 12:53:39 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.01.1003271231190.19615@hp.internal> (raw)
In-Reply-To: <733654e31003270902s7076ef9dxdc17e0ea6e59b987@mail.gmail.com>
On Sat, 27 Mar 2010, Wayne Davison wrote:
> On Fri, Mar 26, 2010 at 8:34 PM, Bart Schaefer wrote:
>
> >
> > http://sourceforge.net/apps/wordpress/sourceforge/2010/03/25/cvs-outage-2010-03-25/
> >
>
> It appears to be back now (was working for me). See:
>
> http://sourceforge.net/apps/wordpress/sourceforge/2010/03/27/cvs-viewvc-are-back-on-line-2010-03-27/
>
> It would be cool to switch from CVS to git (which has better
> high-availability support than CVS),
Really?
I'm a huge fan of git, but if the SF git server were to go down, how is
it any different than the SF CVS server going down? Assuming the goal
isn't to move away from having an 'official' repository, the only
difference obvious to me is that you'd be able to work offline (i.e.
still commit changesets to be pushed later). But, the same is true when
working off of the (unofficial?) git mirror.
I'm definitely *not* saying "Stay with CVS!". Just curious about the
better availability justification.
> [... trimmed other transition-related concerns ...]
--
Best,
Ben
next prev parent reply other threads:[~2010-03-27 16:53 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 [this message]
2010-03-27 18:18 ` Wayne Davison
2010-03-27 19:07 ` Benjamin R. Haskell
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.1003271231190.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).