| 1 | = Why Should Boost Move to Git? |
| 2 | |
| 3 | Subversion works well for Boost's version control needs, so why should we move to Git? |
| 4 | |
| 5 | That's really the wrong question, however. Here are the real questions: |
| 6 | |
| 7 | || 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. || |
| 8 | |
| 9 | == Why should Boost move to a distributed version control system? == |
| 10 | |
| 11 | |
| 12 | |
| 13 | == Why should Boost choose Git as our distributed version control system? == |
| 14 | |
| 15 | Mercurial, Bazaar, and perhaps Fossil are also well developed and supported DVCS systems. They are widely used by well-known open source projects. So why choose Git? |