⏳ A History of Source Control Systems: SCCS and RCS (Part 1) | David Soria Parra
「 Source Control Management (SCM) Systems, have a long and rich history. As the systems evolved, so have their concepts, use cases and adoption over time. While SCMs are ubiquitous in modern software development, they have been fairly novel in the 80s and 90s, and arguable it took the rise of Git and Github for them to be used nearly everywhere 」
A short history of version control systems. It doesn't mention versioning file systems but maybe the author implicitly lumped them under manual systems.
The killer use case for structural diffs and versioning will be comparing reality to the control plane. As opposed to diffing code or the specification.
#dailyreport#emacs#vc#versioncontrol
I answered 15 tricky questions for job at topics of DS, ML,
DL. I used ChatGPT to help me. 😈 All answers should be
correct, I will public my calculations after two week if I
wouldn't get offer. ◕‿◕
I learned VC (Version Control) package for Emacs. ⛏ VC isn't a
mode it is permanently available functionality ⚠, can be used
from file-visiting buffer, Dired buffer, VC Directory buffer.
VC offer very powerful commands: ᕙ( •̀ _ •́ )ᕗ
vc-next-action - universal intellectual action ✭
vc-annotate - for each line, show the latest revision in which
it was modified. ⋆
vc-region-history - Display the history of changes made in the
region of file visited by the current buffer. ★
I learned project management for Emacs with EDE and projectile
and I found it useless. Because Dired + Bookmarks just do the
same.
😶
While building my new site in #11ty, which is a new tool for me, I wonder if it’s time for me to learn #Git and #versioncontrol as well.
I notice that I over and over again make a backup copy of a Nunjucks partial or my eleventy.config.js before trying something (that more often than not breaks some things). And sometimes I lose track on where I’m in my dev process.
Would I benefit from version control? Any relevant tutorials to share?
I don't feel like I can always "control" what git is going to do, with commands sometimes resulting in unexpected behavior that is consistent with the way git works but doesn't track with how I think it should work. Instead, I need to keep a lot in my mind to get it to do what I want.
This introduction to Git aims to "reveal a bit of the simplicity underlying it". I'm not sure Git is as simple as it is to the author, but this work does help understand a little bit more on the tool and amek it feel less confusing:
I know, Git is a mess. But, since we're stuck with it, we may as well try to learn how it works with resources like this, which aims to lead to some form of Git enlightenment.