You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: book/01-introduction/sections/about-version-control.asc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ However, this setup also has some serious downsides.
44
44
The most obvious is the single point of failure that the centralized server represents.
45
45
If that server goes down for an hour, then during that hour nobody can collaborate at all or save versioned changes to anything they're working on.
46
46
If the hard disk the central database is on becomes corrupted, and proper backups haven't been kept, you lose absolutely everything -- the entire history of the project except whatever single snapshots people happen to have on their local machines.
47
-
Local VCS systems suffer from this same problem -- whenever you have the entire history of the project in a single place, you risk losing everything.
47
+
Local VCSs suffer from this same problem -- whenever you have the entire history of the project in a single place, you risk losing everything.
0 commit comments