Knowledge is Power: Getting out of trouble by understanding Git by Steve Smith

[@ruixue6955]

1:23 git is fundamentally a *content-addressable filesystem* with VCS (version control system) under user interface written on top of it 4:51 git internals 5:06 the *first level* of the *git module* - *blob* 5:24 7:59 what a blob is: 9:25 git commit 9:55 3 fundamental types of git objects 10:01 blob 10:10 *tree* - points to the blob 14:10 refs, branches and tags 14:45 *ref* - *a pointer to an object* 14:50 on the simplest level, it is just a file with a string in it 15:23 *branch -* 16:40 *tag*

[@viteok1234]

Smart guy. Clear explanation and understandable. Really the basics which every git user should know . I like this phrase at 4:07 ---> " Once you realize internal model, you realize what commands must exist".

[@Badamski]

This is one of the best git talks I've seen, it deserves way more views.

[@ruixue6955]

19:28 git reset - 19:40 *manipulate a tag or ref* 19:49 what it does is *move* that *pointer back down the tree* 21:01 how do you get back to that previous state. say you've made a mistake here 21:06 you've done a reset 21:40 *git reflog* 23:30 git gc 40:41 get back to the previous status

[@genovo]

Extremely good git talk -- Up through 14:13, some clarification: touching an empty file, may change timestamp, but will not change blob hash inside your git init;

[@ruixue6955]

29:03 git merge 29:40 *git cat-file* to see the tenet of merge 32:20 different merge strategies 37:57 git rebase 39:52 git reset --hard

[@nO_d3N1AL]

This talk isn't the most friendly introduction to understanding Git, especially if you're new to Git, but it's useful to have a technical, in-depth look at it Git in a video format since it's easier to grasp than reading a massive blog post.

[@jonathansawyer01]

Thank you for the excellent presentation!

[@WholeNewLevel2018]

29:21 Nice talk. The arrows are messed up.

[@prashantsingh1096]

Well said. "Just remember the commands and type it ". :)

[@stevecarter8810]

That would be Emma Jane Hogbin Westby. 3/4 is still a respectable score, and that name has good inherent error correction via its low collision rate.

[@jonathansawyer01]

Excellent !!!

[@lgylym]

Good work. Thank you.

[@maik-beckmann]

Very good information, very well done slides. A minor ciritc: Sometimes it's very hard to audibly understand the presenter, due to extreme talking speed.

[@mdturnerinoz]

The way I learned git there were FOUR basic objects in git: the three you mentioned and the fourth are hard tags (git tag -a tag name). Has this changed?

[@Dominic_Muller]

+Marty Turner There are tags, yes, but intros tend not to mention them as they aren't required for understanding the model.

[@Arcsecant]

I'm very sad that the arrows point the wrong way round. 😥 Advanced talks should have them point from child to parent.

[@michaelkohlhaas4427]

Are you blind?

[@halilkarakose]

Very informative presentation. Slides can be found: www.slideshare.net/tarkasteve/knowledge-is-power-getting-out-of-trouble-by-understanding-git I found "reflog + reset = redo" slide very helpful. See minute 40:00

[@LeviMcCormick]

He references this video: Teaching People Git, Emma Jane Hogbin Westby - Git Merge 2015 kzbin.info/www/bejne/rorLeZxurrBgf9U

[@DisfigurmentOfUs]

nice

[@robhein7573]

"reset manipulates a ref" - which one? "git reset --hard feature^" - what is "feature" in this context? arrow with the word "feature" moves back one commit - what does the "feature" arrow represent? "hard completely destroys this and checks it out again" - destroys what? "reset manipulates the branch head" - what is a head? "^ means parent" - parent of what? "the reason I do prune all is because I'm forcing the situation" - huh? "merges keep the context of the feature's commits" - what context? By "feature" do you mean branch? "a ff merge shifts the head forward as if nothing happened" - nothing happened? A topic this complex demands more concise language.

[@notker88]

nice content but he does not speak very clearly :( it's very hard to understand him