So You Think You Know Git - FOSDEM 2024
GitButler1 HN recommenders · 2024–2025
1.6M views · talk · evergreen · Uploaded 2024-02-08
Scott Chacon's FOSDEM 2024 talk on lesser-known Git tips and tricks: useful config settings, older and newer commands, monorepo and big-repo features, and recent GitHub additions. It closes with why he is now building GitButler, followed by a Q&A.
HN commenters point to it as a well-regarded tour of newer, lesser-known Git features, and it is among the most-watched engineering talks of 2024.
38:47RailsConf 2014 - All the Little Things by Sandi Metz
Confreaks
40:20"Testing Distributed Systems w/ Deterministic Simulation" by Will Wilson
Strange Loop Conference
1:03:55🚀 TDD, Where Did It All Go Wrong (Ian Cooper)
DevTernity Conference
54:20Bret Victor - Inventing on Principle
Rui Oliveira
1:02:26Solving Problems the Clojure Way - Rafal Dittwald
Clojure/north
52:35Debugging Under Fire: Keep your Head when Systems have Lost their Mind • Bryan Cantrill • GOTO 2017
GOTO Conferences
42:15"Performance Matters" by Emery Berger
Strange Loop Conference
23:16A Tour of the Acme Editor
Russ Cox
4 comments from Hacker News
I remember watching your FOSDEM talk on YouTube, where you asked whether people have rerere turned on _and_ know what it is, in one question. I have it on, but only the faintest of clues what it is! Just git things, I suppose. [VIDEO]
> I'd say that perhaps Git is unsuitable above certain thresholds on numbers of files Scott Chacon in a recent talk about git[0] said that Microsoft uses git to version control Windows. They have ~3.5 million files in the repo, which is about 300 gigabytes in size. There are some tweaks to improve git performance in those scenarios; but still, I'd say it's a pretty impressive threshold. [0] - [VIDEO]
I know these are conferences that they track, but I happen to know the Scott's talk from FOSDEM titled "So You Think You Know Git?" is at 1.3m million views: [VIDEO]
You could do a blobless or treeless clone [LINK] Combined with --depth=1 and the --no-checkout / --sparse-checkout flow that the GP already described. I just tested on the emacs repo, left column is disk usage of just the `.git` folder inside: Shallow clones (depth=1): 124K: Treeless clone depth=1 with no-checkout 308K: Blobless clone depth=1 with no-checkout 12M: Treeless clone depth=1 sparse checkout of "doc" folder 12M: Blobless clone depth=1 sparse checkout of "doc" folder 53M: Treeless clone depth=1 non-sparse full checkout 53M: Blobless clone depth=1 non-sparse full checkout 53M: Regular clone with depth=1 Non-shallow clones: 54M: Treeless clone with no-checkout 124M: Blobless clone with no-checkout 65M: Treeless clone sparse checkout of "doc" folder 135M: Blobless clone sparse checkout of "doc" folder 107M: Treeless clone with non-sparse full checkout 177M: Blobless clone with non-sparse full checkout 653M: Full regular git clone with no flags Great tech talk covering some of the newer lesser-known git features: [VIDEO]