floof.org

Pippin friendica

"git" has always felt a bit unknowable/un-understandable to me. I've read documentation, I've played with it a few times, and I've fetched and checked out repositories many times, but I've never really gained an understanding of it enough to use it for myself for any real project.

For example, I was never quite able to remember (reliably enough to rely on anyway) how to pull updates from a remote repo to a local one and update the checked-out copy to the latest (and in Mercurial, those would be the steps, but git seems to have other ideas, like "stashed" or "staged" files? and maybe no clear concept of what "latest" is? I don't know, I haven't bothered trying to learn it for years now so it's very hazy), so after I tried to update a checked out copy I'd then re-clone a fresh new copy of the remote repo and diff the two to find out if I'd managed to update it successfully. Sometimes I'd skip the hassle of trying to remember how to pull updates and just re-clone.

I used to use Mercurial (hg) (still not a lot; I've never really used any VCS very much), which I happened to choose over git back when they were relatively new β€” the two came out just days apart 21 years ago and Mercurial just seemed less of a mess and more understandable and predictable at the time β€” but I've not really used any VCS for years now. I mainly only write things like shell scripts and configuration files and fiction, and I tend to just keep numbered backup† copies alongside the current version β€” it's good enough for me. And almost all of what I write is symbiosisware anyway, so all I need is something minimal that works for me.

However, I've just read the README in the first commit in the "git" repository and I feel that has given me more insight into how git works than all the documentation I've ever read on the subject. It makes it make some sense. I can see the shape of how a VCS could be built on top of those primitives/data structures. I now feel like I have a sense of what the underlying data structures look like, so I feel like I could now read more current git documentation and actually get something useful from it. Previously I've felt that just about anything I've read about git assumed I already knew all the concepts. (Or was a introductory tutorial which didn't go into the underlying concepts, just tried to teach the surface workflow and procedures to use it.)

How did I get there? Saw a recent post by SGT, followed links, ended up on his "symbiosisware" page, searched to see if other people used the term, and found the link to the first git commit on this page.

---
† Yes, I also have proper automated backups; these numbered "backups" are for history, not data security.


@domi re sidenote: thank you!

The window decorations are the 'Crux' theme from the Sawfish window manager, which I mostly use for its programmability rather than its looks (although I agree Crux is pretty nice).

The font is my own work, on my website but still in "unfinished" status: https://www.chiark.greenend.org.uk/~sgtatham/technicality/

The choice of PS1 is designed so that it turns into a no-op shell statement, so that I can copy-paste a whole line from one terminal to another without having to carefully not select the prompt at the start. It's coloured using something that isn't one of the standard 8 ANSI colours so as to be easily distinguishable from _most_ other terminal output, in the expectation that most things will stick to the usual 8.

(ok, and also because purple is cool)