From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: Bart Schaefer <schaefer@brasslantern.com>,
zsh workers <zsh-workers@zsh.org>
Subject: Re: Sourceforge GIT is down
Date: Sun, 19 Jul 2015 17:19:27 +0000 [thread overview]
Message-ID: <20150719171927.GE1900@tarsus.local2> (raw)
In-Reply-To: <CAHYJk3RU5xa2PU8cw6-HCG=pTbEVximbmxN3eNgKYGaK-=4FgQ@mail.gmail.com>
Mikael Magnusson wrote on Fri, Jul 17, 2015 at 03:47:56 +0200:
> On Thu, Jul 16, 2015 at 11:00 PM, Bart Schaefer
> <schaefer@brasslantern.com> wrote:
> > fatal: unable to connect to git.code.sf.net:
> > git.code.sf.net[0: 216.34.181.155]: errno=Connection refused
> >
> > The Blog page says:
> >
> > The sourceforge.net website is temporarily in static offline mode.
> > Only a very limited set of project pages are available until the main website returns to service.
>
> Should we set up an official secondary repo, or at least public
> mirrors of all our (the developers') repositories? Eg, either a
> cvs-like repository like the sourceforge one is, or everyone just has
> their own repos somewhere. Or both would be fine too. (Mine is
It's tricky to have a second repository to push commits to. For
example, there is the split-brain problem: what to do if the two master
repositories diverge, and the changes made to one conflict with the
changes made to the other?
Then there is authentication, glue code to keep the two masters in sync,
and so on.
Cheers,
Daniel
> available at http://cgit.mika.l3ib.org/cgit/zsh-cvs/ for example).
> There's also this automatic readonly mirror of the sourceforge repo,
> http://repo.or.cz/w/zsh/mirror.git
>
> --
> Mikael Magnusson
prev parent reply other threads:[~2015-07-19 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 21:00 Bart Schaefer
2015-07-17 1:47 ` Mikael Magnusson
2015-07-18 20:38 ` scowles
2015-07-19 9:34 ` Axel Beckert
2015-07-19 17:19 ` Daniel Shahaf [this message]
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=20150719171927.GE1900@tarsus.local2 \
--to=d.s@daniel.shahaf.name \
--cc=mikachu@gmail.com \
--cc=schaefer@brasslantern.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).