| 3 | | [http://git.or.cz/course/svn.html Git - SVN Crash Course] |
| 4 | | [http://gitready.com/ Git Ready - knowledge base for git] |
| | 3 | There are very many resources on the web where you can learn about Git. See the two resources below to get started. Furthermore, this page will discuss three concepts that you need to grasp in order to get started. |
| | 4 | |
| | 5 | * [http://git.or.cz/course/svn.html Git - SVN Crash Course] |
| | 6 | * [http://gitready.com/ Git Ready - knowledge base for git] |
| | 7 | |
| | 8 | == Centralized versus Distributed == |
| | 9 | |
| | 10 | One of the main concepts to understand in the difference between Subversion and Git, is the difference between centralized and distributed version control. This is a topic much written about, and it would be a duplication to work it all out again. Have a look at [http://media.pragprog.com/titles/tsgit/chap-002-extract.html Chapter 2 of the Pragmatic Version Control Using Git] book. |
| | 11 | |
| | 12 | The organization of the workflow will be using a **shared repository**. That means that on git.haiku-os.org there will be a repository that core developers are able to push to. In a sense this closely resembles the model of subversion, with the difference that everybody can start their own repository, and share it in order to collaborate on a feature before it is pushed into the centralized repository. |
| | 13 | |
| | 14 | See this image graciously borrowed from the aforementioned book: |
| | 15 | [[Image(http://media.pragprog.com/titles/tsgit/images/repo-shared-simple.png)]] |
