Ted Nyman – High Performance Git

I'm only on to chapter two and already it's explained some plumbing details that I somehow have missed all these years. This is great

Perfect read for the project I'm working on, which uses git as an auditable backend storage! (The project is an open source multisig signoff solution: all multisig definitions and signatures collected are stored in a git repo you can clone, see https://asfaload.com/ )

> LFS adds its own operational overhead.

Seemingly seconds on every remote-touching command, even on a very small repo.

ted nyman: #1 most knowledgable college football fan in sf

and also git

which makes more sense i guess

I've been wanting to ask this:

Why isn't

    git clone --depth 1 ... 

I would guess that for at least 90% of the repos I clone, I just want to install something. Even for the rest, I might hack on the code but seldom look into the history. If I do then I could do a `git fetch` at that point and save the bandwidth and disk space the rest of the time.