git’in jiggy with git
DESCRIPTION
A brief overview of the distributed source control system known as GitTRANSCRIPT
![Page 1: Git’in Jiggy With Git](https://reader033.vdocument.in/reader033/viewer/2022051818/54b783174a7959db528b464b/html5/thumbnails/1.jpg)
Git’in Jiggy With Git
With your co-host: Will Smith!
![Page 2: Git’in Jiggy With Git](https://reader033.vdocument.in/reader033/viewer/2022051818/54b783174a7959db528b464b/html5/thumbnails/2.jpg)
Why?
• Linux kernel devs got upset at BitKeeper because it went closed source
• Linus Torvalds (the Linux guy) designed his own distributed source control– Take CVS as an example of what NOT to do– Support a distributed workflow– Strong safeguards against corruption (accidental or malicious)– High performance
• Started development April 3rd, 2005• Was used for Linux kernel 2.6.12 (June 16th)• Version 1.0 came out on December 21, 2005
![Page 3: Git’in Jiggy With Git](https://reader033.vdocument.in/reader033/viewer/2022051818/54b783174a7959db528b464b/html5/thumbnails/3.jpg)
What’s the Deal?
• Distributed source control system– Each developer has a complete history of the
source, and could easily serve as the “master repository”
• Focused on Branching & Merging• Damn Fast
![Page 4: Git’in Jiggy With Git](https://reader033.vdocument.in/reader033/viewer/2022051818/54b783174a7959db528b464b/html5/thumbnails/4.jpg)
What a commit looks like
TimestampWed, Nov 9th, 10:37 AM
Message“Checkin’ in teh codez”
Tree Object (file) Reference(s)/dev/codez/Will_Smith.cs
Parent Reference89adf523ad1234Previous commit
![Page 5: Git’in Jiggy With Git](https://reader033.vdocument.in/reader033/viewer/2022051818/54b783174a7959db528b464b/html5/thumbnails/5.jpg)
Git is a big-ass linked list!
First! Last Commit
![Page 6: Git’in Jiggy With Git](https://reader033.vdocument.in/reader033/viewer/2022051818/54b783174a7959db528b464b/html5/thumbnails/6.jpg)
How do we keep track of everything!?
First! Last Commit
Develop!
Version 4.2!
REFERENCES!
![Page 7: Git’in Jiggy With Git](https://reader033.vdocument.in/reader033/viewer/2022051818/54b783174a7959db528b464b/html5/thumbnails/7.jpg)
Staging
Commits, How Do They Work?
First!
Develop
New Commit
![Page 8: Git’in Jiggy With Git](https://reader033.vdocument.in/reader033/viewer/2022051818/54b783174a7959db528b464b/html5/thumbnails/8.jpg)
Doing it wrong: Branching
ALL TEH FILEZ COPY OF ALL TEH FILEZ
BRANCH!
![Page 9: Git’in Jiggy With Git](https://reader033.vdocument.in/reader033/viewer/2022051818/54b783174a7959db528b464b/html5/thumbnails/9.jpg)
Doing it Right: Branching!
First!
Develop
New Branch!
![Page 10: Git’in Jiggy With Git](https://reader033.vdocument.in/reader033/viewer/2022051818/54b783174a7959db528b464b/html5/thumbnails/10.jpg)
Merge!
First! 2
1 3 4
Develop
Feature
Current Position
Merge Commit
![Page 11: Git’in Jiggy With Git](https://reader033.vdocument.in/reader033/viewer/2022051818/54b783174a7959db528b464b/html5/thumbnails/11.jpg)
All Your Rebase R Belong To Us
First!
Develop
Feature
Current Position
![Page 12: Git’in Jiggy With Git](https://reader033.vdocument.in/reader033/viewer/2022051818/54b783174a7959db528b464b/html5/thumbnails/12.jpg)
Working With RemotesOrigin
Local
“Clone” “Pull”“Push”
![Page 13: Git’in Jiggy With Git](https://reader033.vdocument.in/reader033/viewer/2022051818/54b783174a7959db528b464b/html5/thumbnails/13.jpg)
Github.com is AWESOME.