Git Going at JavaZone 2010

1,543 views

Published on

Matthew McCullough's presentation of Git to the JavaZone 2010 conference in Oslo, Norway

Published in: Education
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,543
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Git Going at JavaZone 2010

  1. 1. TC HI NG S WI TO G IT by Matthew McCullough Ambient Ideas, LLC
  2. 2. I S ubv ers ion 20 00
  3. 3. I Pr oductiv ity
  4. 4. I Git
  5. 5. LICITY SIMP
  6. 6. git -scm.org
  7. 7. put binaries on your $PATH
  8. 8. cd to a root of where you will store the repository
  9. 9. git init and a new repository is created in the current directory
  10. 10. create some files to be tracked git add . and they are staged for committing
  11. 11. Staged?
  12. 12. Staged?
  13. 13. when satisfied with the files you’ve staged git commit and they are transactionally stored into the repo
  14. 14. SP E E D
  15. 15. etterthanx.com w hygitisb
  16. 16. Init 0.56s 0.02s git init svnadmin create data from http://whygitisbetterthanx.com/#git-is-fast
  17. 17. Diff 12.21s 0.55s git diff svn diff data from http://whygitisbetterthanx.com/#git-is-fast
  18. 18. Branch 3.16s 0.08s git branch svn copy data from http://whygitisbetterthanx.com/#git-is-fast
  19. 19. Tag 2.30s 0.06s git tag svn copy data from http://whygitisbetterthanx.com/#git-is-fast
  20. 20. Status 2.26s 0.47s git status svn status data from http://whygitisbetterthanx.com/#git-is-fast
  21. 21. BILITY OMPATI C
  22. 22. ...it would be nice if Git worked with SVN
  23. 23. git svn clone and the entire Subversion history is replicated as a Git repository
  24. 24. git svn dcommit and your Git commits are transactionally replayed to the Subversion server
  25. 25. NECT ED IS CON D
  26. 26. Chained to a network
  27. 27. more available connectivity
  28. 28. more demand to work without connectivity
  29. 29. Which Git commands run offline? all of them!
  30. 30. ‣ git status ‣ git branch ‣ git log ‣ git revert ‣ git blame
  31. 31. ‣git reset ‣git clean ‣ git merge ‣ git remote ‣git pull ‣git push ‣ git fsck ‣ git repack
  32. 32. RATI ON OL LA BO C
  33. 33. git push and the missing objects are copied to a local or remote host
  34. 34. git pull and the missing objects are copied from a local or remote host
  35. 35. gitserve . and the repository(ies) are shared on the network via the git:// protocol
  36. 36. U S CL E M
  37. 37. Bisect
  38. 38. when the unit tests are broken git bisect and find the culprit
  39. 39. if you forget when a constant was added git grep and find the commit that added it
  40. 40. GitHub.com
  41. 41. NG HIE D S WI TC TO G IT by Matthew McCullough Ambient Ideas, LLC matthewm@ambientideas.com
  42. 42. Credits • Ferrari: http://flic.kr/p/7wL8zV • Ferrari: http://flic.kr/p/3akVWt • Ferrari: http://flic.kr/p/4bDjbF • Ferrari: http://flic.kr/p/7Ki31g • Ferrari: http://flic.kr/p/7xPC9E • Ferrari: http://flic.kr/p/4x9q4g • Knife: http://www.flickr.com/photos/36314420@N03/3422572002/

×