Re:BitBucket was down
by staticshock on Sunday April 27, 2014 @10:11AM
(#7655116)
I'm not sure if you're making a joke and/or english is not your first language, but, for the record, I think you're looking for the word "outage", not "outrage".
That's a typo. Thank you. And this has nothing to do whether English is my first or second or third language. I can be completely fluent in English and still have a typo.
So next time, just say "you meant outage" is good enough.
Re:BitBucket was down
by jmaygarden on Sunday April 27, 2014 @10:58AM
(#7655303)
You misspelled the word consistently with each usage. I thought you were trying to be funny. So, it wasn't clearly a typo to two distinct readers.
PS - It looks like you edited the second outrage, but not the first.
I used to use BB a lot, almost daily, last year. I would occasionally hit one of those "ssh issue" or "outage". The most problematic is BB cannot close issues automatically via commit message on some repositories. Some. It's rather annoying.
If you consider using BB or Github for real product, I advise you host yourself a server running either Gitlab or SCM-Manager (supports git, mercurial, svn) and when you push you should push to your "local" server and the remote server. This way you can still do some remote work during downtime without sending patches around. This is an option if you truly need a backup plan...