* **fork**: create an exact copy of a remote repository, at that point in time, in your personal GitHub account.

Everything you code will end up in your personal repository after you `push`. * **origin**: your **personal repository**. Both Kodi's **main repository** and your **personal repository** are remotes.

* **remote**: the remote location of a repository, usually on some central server. It is where all the code integration happens. * **master**: the repository's main branch.

It's where everything you code will end up after review and a pull request (PR for short) is merged. * **repository**: a place where files and their versioned history live. Some of the most important ones are outlined below. It is not the most easy version control system (VCS for short) to work with but it is very intuitive **once** you understand some concepts. **()** is a distributed version control system, originally written by a brilliant, self-described **()**. **(#92-fetch-a-pull-request-someone-submitted-to-your-repository)**ĩ.3. **(#63-push-local-feature-branch-to-origin-and-sync-remote-feature-branch-with-it)**ħ. **(#62-fetch-feature-branch-from-origin-and-sync-local-feature-branch-with-it)**Ħ.3. **(#61-fetch-master-branch-from-upstream-and-sync-local-master-branch-with-it)**Ħ.2. It is streamlined to Kodi's **()** development workflow: create feature branch, write awesome code, open a pull request, get it reviewed by Kodi team members, merge pull request. It will help you get acquainted with command-line `git`, even if you never imagined yourself touching the dreaded beast with a 3m pole (that's 10 feet for those across the pound). This guide is intended as a **simple, non-exhaustive, git reference source**.

Download kodi 15.2 rc2 for windows 7