The Centurion project team has moved on GIT, see why and how. http://centurion-project.org

1. Easy versioning with GIT Yes it can

2. No! No different! Only different in your mind. You must unlearn what you have learned Master Yoda Git from day to day Before Now svn up git pull svn commit git commit Is this really harder than before ?

5. Staging area

6. Snapshot of the diff that will be committed on next “commit”

7. Repository

10. Unmodified

11. File in WT is the same than the one from the repository

12. Modified

13. File in WT has been modified and not committed yet

14. Staged

16. Branching What for? Work in an environment as stable as possible Avoid conflict that slow productivity (for others) Being able to integrate new features one by one This is true for every versioning tools ! But GIT is amazingly fast for these branching operation (so fast that the “cheap branching” has appeared)

17. Branching git branch iss53 git checkout iss53 … git commit

18. Branching git checkout master git merge iss53

19. Branching One branch for the stable release One branch for development (testing) One branch per topic (short development) branched from the dev branch

21. Learn how to use “git remote” command (and sisters commands)

23. gitpull/fetch [repository] [refspec]

25. Workflow Integration manager

26. Workflow (example) A contributor clones a repository and makes changes. The contributor pushes to their own public copy. The contributor sends the maintainer an e-mail asking them to pull changes. The maintainer adds the contributor’s repo as a remote and merges locally. The maintainer pushes merged changes to the main repository.

27. Credits Slides made by Mathias DESLOGES (Centurion Core Developer) : http://centurion-project.org/ Figures and examples are taken from the excellent “Pro Git” web site : http://progit.org/

28. The End