Changes between Version 4 and Version 5 of Git/WhyGit

Timestamp:

Feb 6, 2011, 9:18:34 PM (12 years ago)

Author:

Beman Dawes

Comment:

--

Git/WhyGit

@@ -15 +15 @@
 == Why should Boost move to a distributed version control system? ==
 
-* Enables decoupling and modularization. While decoupling and modularization is certainly possible with non-distributed version control, a distributed version control system makes it much easier, and many large open-source projects have moved or are moving to DVCS.
+* Enables decoupling and modularization. While decoupling and modularization is certainly possible with non-distributed version control, a distributed version control system makes it much easier. As a consequence, many large open-source projects have moved or are moving to DVCS.
 
 * Decouples the Boost mothership repository from developers' local repositories:
@@ -37 +37 @@
 ==  What is the downside of Boost using distributed version control and Git? ==
 
-* Will the real Boost step forward?
+* Will the real Boost step forward? A proliferation of Boost repositories can be a source of confusion unless care is taken.
+
+* The migration itself will cause a certain amount of disruption.
+ (transient).
+
+* Those who just don't care will have to learn a new tool.
+ (transient, subjective).
+
+* Links to svn will be broken.  Trac and svn are currently
+ heavily cross-linked. (long-term).
+
+== Acknowledgments ==
+
+Dave Abrahams helped clarify decoupling and modularization as driving forces.
+
+Steven Watanabe supplied several of the "downside" entries.
 
 || Aside: The Wikipedia article on [http://en.wikipedia.org/wiki/Distributed_version_control_system Distributed revision control] as of 2 Feb 2011 is weaker than usual and may be misleading. Don't draw any conclusions based on it. ||