5 ms·
What "op" exactly? git push/pull? git push/pull are bandwidth efficient and atomic. A failed pull/push wont destroy your local/remote copy.
by babas 13y ago
What "op" exactly? git push/pull? git push/pull are bandwidth efficient and atomic. A failed pull/push wont destroy your local/remote copy.
- Argorak 13y agoIt tends to drop your connection on large packs. Thats more a server configuration thing, many git hosts disconnect slow clients. I was in Botswana for a few weeks in November and I can relate to that sentiment: git was unusable down there.
- midas007 13y agoYuck, BTDTBTTS. Satellite latency is eye-stabbing, almost as bad as the utterly worthless Mountain View's Google Wi-Fi. Local internet elsewhere, in random countries, GFL... bring your own or start a service (yeah, a friend made some serious cash putting up a service on some Greek island). Anyone on OSX can feel some pain just by enabling Network Link Conditioner prefpane by creating a profile as follows: Download Bandwidth: 256 Kbps Downlink Packets Dropped: 90% Downlink Delay: 1000 ms Uplink Bandwidth: 256 Kbps Uplink Packets Dropped: 90% Uplink Delay: 1000 ms DNS Delay: 2000 ms Setup instructions: http://mattgemmell.com/network-link-conditioner-in-lion/ http://mattgemmell.com/network-link-conditioner-in-lion/
- midas007 13y agoThe issue is never being able to complete the fetch or push because of a spotty network. It goes without saying that source control should not screw up my local or remote copies.