On Fri, Jul 15, 2011 at 5:19 AM, Cam Smith <[email protected]> wrote:
> Seems to be the git:// server. Once I updated my remotes to point to > https:// instead, I could pull updates again. > Our bad. One of our servers crashed while our hosting provider was doing maintenance on it, and we had made some changes to our git-proxy script that caused it to fail being started. Christian was quick in fixing that, and everything is back to normal. We're really sorry this happened, and will change our deployment strategy so these errors are caught while deploying, not when rebooting the servers further down the road. Cheers, - Marius -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected]
