zlacker

The whole point of DVCS is that everyone who's run `git clone` has a full copy of the entire repo, and can do most of their work without talking to a central server.

Brief downtime really only affects the infrastructure surrounding the actual code. Workflows, issues, etc.

>>TillE+(OP)
> Brief downtime really only affects the infrastructure surrounding the actual code. Workflows, issues, etc.

That's exactly the point. This infrastructure used to be supported by email which is also distributed and everyone has a complete copy of all of the data locally.

Github has been slowly trying to embrace, extend, and extinguish the distributed model.

>>418tpo+hi
You can enable all email notifications and respond to them without visiting the site. If you like to work like that, you still can.

>>virapt+yq
The site is the thing that sends those email notifications, and receives your responses to them. So if GitHub is down, that won't work.

GP is talking about directly emailing patches around or just having discussions over email. Not intermediated through GitHub.

>>sixstr+lw
Yes, but this solves one part of the problem - accessible archive. Then you can revert to emailing people directly while the system is down.