The first release of git was in 2005, around a decade after Windows 95.
Diff3 is from 1979 (https://en.wikipedia.org/wiki/Diff3), so three-way merges (https://en.wikipedia.org/wiki/Merge_(version_control)#Three-...) predate git by decades.
Win 95 feels from era1, xp and git was already in era 2.
Once those two changes were done by 2010 though, there’s been no game changer, if anything we've regressed through shittyfication (we seem to have fewer social networks vs the original Facebook for example, as most of them turned single player feed consumption).
Maybe pre and post LLMs will feel like an era change in a decade as well?
Same year I deleted all our customer's websites by simply dragging the hosting folder somewhere into C:\programs or something by mistake... A double click + lag turned into a drag and drop! Whoops!
I was pale as a ghost as I asked for the zip drive.
We had to reboot the file server first, which we did a swift kick to the power button.
At least today we employ very secure mechanisms; like YAML rollouts of config, to keep things interesting.
But the percentage is probably small, yes.
Google still uses a clone of Perforce internally (and various wrappers of it). Perforce was released in 1995.
For code, I prefer git as I said, but in a game's depot most files are not code, and Perforce is built around handling those other assets well.
Of course, `git send-email` has a plethora of options, e.g. you'd typically add a cover letter for a patch set.
Also, in the Linux kernel tree, there are some additional helper scripts that you might want to run first, like `checkpatch.pl` for some basic sanity checks and `get_maintainer.pl` that tells you the relevant maintainers for the code your patch set touches, so you can add them to `--cc`.
The patches are reviewed/discussed on the mailing list that you sent them to.
On the receiving side, as a maintainer, you'd use `git am` (apply mail) that can import the commits from a set of mbox files into your local git tree.
> ...and I immediately got flamed by several people because no one used patches any more.
How are these ideas connected? The intent of git is that you work with patches.
Unlike patches, pull requests aren't even a feature of git.
It just really highlights how much better BitKeeper and then Git's design was compared to what came before. You then pile on being free/OSS, and being "proven" by an extremely large, well known, and successful project on top, and you have yourself explosive growth.
There are developers around these days who never had the displeasure of using the pre-Git source control offerings; it was rough.
Priceless.