This is why I love git (and distributed version control systems in general). For the most part a short downtime isn't the end of the world. When it comes back up I'll push my changes and that'll be that.
Github experiencing major service outages across all services.
11–20 of 147 posts
Re: Github experiencing major service outages across all services.
#12And this is why I use Google Code: supports git and is more reliable than Github. It's a shame that they don't offer a paid service for closed-source software.
Re: Github experiencing major service outages across all services.
#13That's a really nice status dashboard, tracking and publicly displaying your 98th% is really cool. On the other hand stuff like this: "13:17 UTC We are seeing unicorns ..." Comes off as un-professional at exactly the wrong moment.
This is more professional reporting than most companies do.
Re: Github experiencing major service outages across all services.
#14This is why I love git (and distributed version control systems in general). For the most part a short downtime isn't the end of the world. When it comes back up I'll push my changes and that'll be that.
I can do the same thing with CVS?
He can.
Re: Github experiencing major service outages across all services.
#15Re: Github experiencing major service outages across all services.
#16That's a really nice status dashboard, tracking and publicly displaying your 98th% is really cool. On the other hand stuff like this: "13:17 UTC We are seeing unicorns ..." Comes off as un-professional at exactly the wrong moment.
Gives me the impression there are actually real people trying to fix things, not just blank-faced robo admins following company policy HOWTO-Fix guides.
That github isn't a blank sheet devoid of life and emotion and all 'professional' is the reason I'm willing to shrug off downtime like this.
If anything, I really feel for whoever posted:
We do not expect this to have visible impact to
customers, but will update status if that changes.
Ouch. You never ever want to follow that up with a post in red.Re: Github experiencing major service outages across all services.
#17This is why I love git (and distributed version control systems in general). For the most part a short downtime isn't the end of the world. When it comes back up I'll push my changes and that'll be that.
(Though I do wish GitHub Issues weren't as centralized...)
Re: Github experiencing major service outages across all services.
#18This is why I love git (and distributed version control systems in general). For the most part a short downtime isn't the end of the world. When it comes back up I'll push my changes and that'll be that.
Re: Github experiencing major service outages across all services.
#19That's a really nice status dashboard, tracking and publicly displaying your 98th% is really cool. On the other hand stuff like this: "13:17 UTC We are seeing unicorns ..." Comes off as un-professional at exactly the wrong moment.
How is that un-professional? Unicorns mean errors for github, and they report them. This is more professional reporting than most companies do.
I have no idea what this means, but I can see how the idea of coming up with an alternate language in which fantasy creatures represent things we already have established words for might seem unprofessional
Re: Github experiencing major service outages across all services.
#20This is why I love git (and distributed version control systems in general). For the most part a short downtime isn't the end of the world. When it comes back up I'll push my changes and that'll be that.
I would point out that both TFS and Mercurial do the same thing (as does ClearCase, but ClearCase is awwwful), but with much less memory consumption on the local PC. Not trying to add snark (I upvoted the above comment), just adding that it's not a GitHub feature.
Well, no, obviously it's a feature of Distributed Version Control Systems in general.
In fact, that's probably why OP wrote "This is why I love git (and distributed version control systems in general)" and didn't in any way claim it was a feature of GitHub?
And do you have some kind of reference for git being less memory-efficient (are you talking RAM-wise?) vs Mercurial or TFS? On its face its pretty hard to believe; git is pretty light-weight.