I've used cvs a bit recently.
It's amazing how poor the performance is on large repositories, even on modern machines.
I can't figure out how I put up with this 20 years ago.
Now we're so completely absorbed by the screen for so long, we get irritated by any perceived delay.
Learn the basics of C and Perl for automation, Perl can do tons of *unix stuff (awk/sed... but better).
Mark Burguess has books on Perl/C (ANSI C and GNU C) and the basics of C++ with systems' programming. I know today Golang would be more apt but if you know how the things work under the shiny stuff, you will apply most of the knowledge from Unix systems' programming to Go in a breeze.
Once you begin to automate scripting, testing and repetitive stuff, you will spend less time with computers.
This said, you can and should slow it down if you feel overwhelmed, generally speaking. Use reminders to break every 45 minutes or so, then stand up and walk around. Take longer lunches. Generally speaking, lower expectations about your productivity - which, in itself, should not be a life goal. The cult of productivity helps capital, not people. We should be kinder to ourselves.
I guess that's why the errata page has source patches. It's also great that they have syspatch now for fast binary patches
No. In the bad old days, for many people version control software wasn't sufficiently better (and in some respects much worse) than just not using any. So many people didn't use any.
> Recall that git was also designed to work over mailing lists. git format-patch, git apply, etc.
Right, and when you do web things with that same git in 2024, it looks and works like it's 2024.
You could use an old git server/file browser UI, or the built-in gitweb[0] for example, but you don't, you use something more modern & featureful, working better on mobile, looking prettier, etc. Even Linux (with its history intertwined with git) uses Github[1] as its mirror, not gitweb or anything looking like the link above for OpenBSD.
That's the way everybody used to work?
I can't recall if there were local x11 visualizing tools like gitk is today. (Google says tkcvs) I remember there were some graphical diff programs, you could set an environment variable and make the "cvs diff" command show something nicer looking.
Recall that git was also designed to work over mailing lists. git format-patch, git apply, etc.