So You Think You Know Git - FOSDEM 2024

"fucking nerds...". Golden

I know I don't know git, that's why whenever I have to do something new I research it for 30 minutes and then make a script so I don't have to do that again. Mad respect to all y'all who somehow find the time to master git and all the other devops wizardry on top of learning your language of choice.

Suggestion: add chapters (timestamps) to this video. It really helps when you're watching for the second time!

The excitement level of this guy is priceless. Imagine working with him in a team!

Great talk, I really appreciate the "shotgun" style presentation - it cuts the crap while keeping it clear.

Timestamps for dorks: 00:00 - Introduction 01:06 - About Me (well, Scott Chacon) 02:36 - How Well Do You Know Git? 05:09 - Our Agenda 06:25 - Some Helpful Config Stuff 09:42 - Oldies But Goodies 16:22 - Some New Stuff (You May Not Have Noticed) 23:48 - Some Big Repo Stuff / Monorepo Stuff 33:29 - Some New Github Stuff 35:54 - GitButler 36:50 - End of talk 37:03 - Start of Q&A Session 37:06 - Q: Why does GitHub not do git range diff? 38:28 - Q: Why do submodules suck everywhere? 40:16 - Q: With SSH signing, is it possible to specify more than one key? 40:42 - Q: Why can't --force-with-lease be the default force? 42:33 - Q: If you were back on the Git development team, what direction would you like to see it move in? 44:58 - Q: We all love the Git CLI - but do you ever use any visual tools? 46:41 - That's all folks!-

The talk is great, but the manner of it being presented is even better!

`git blame -C -C -C` is pure gold. But wait, there's more! From `GIT-BLAME(1)` -C[] In addition to -M, detect lines moved or copied from other files that were modified in the same commit. This is useful when you reorganize your program and move code around across files. When this option is given twice, the command additionally looks for copies from other files in the commit that creates the file. When this option is given three times, the command additionally looks for copies from other files in any commit. is optional but it is the lower bound on the number of alphanumeric characters that Git must detect as moving/copying between files for it to associate those lines with the parent commit. And the default value is 40. If there are more than one -C options given, the argument of the last -C will take effect.

Next to being an informative talk, the way it's presented is great. Good job on that presentation skills!

Excellent talk! After many years on Youtube this made me create a new playlist of videos I need to rewatch regularly. The bar has been set pretty high!

Fantastic speech! Thank you, Scott. So many cool things about Git.

Really excellent talk. Incredible pacing, funny, and lots to learn for folks at every level.

Fantastic presentation!

looking forward to gitbutler. awesome talk!!

Didn't know that guy before, immediately caught fire because of his excitement, bought his book after the first 10 minutes. Great talk!

Thanks for the book. It saved my neck in 2011. Every intern I've had since 2012, on their first day, I give them the book and ask them to read it all, and do all the exercises. I give them paper so they can mark it up as needed. Every intern that does this, has no issues with git all summer. The one or two interns that did not do the exercises? They struggle. Great book!

What a great talk. Thanks :)

Time 8:13 - Setting or defining work and oss (open source software) directories. Thank you, Scott!

Wow. What a great presentation. Thank you very much.

So excited to share this with my boss Mike, he's our local Git wizard and I'm so thankful for him. He's always so excited to share the new things he's learned and I'm looking forward to paying it forward!