Git for Hardware Folks, Part One
ฝัง
- เผยแพร่เมื่อ 26 ต.ค. 2023
- What the heck is Git, and why do I care? That's what I thought, too. Then I started learning programming so that I can make Adafruit Feather boards, microprocessors, do what I want. The need for managing versions of software and collaborating with other people made it clear. I needed to learn about Git. And Ike offered to help, and suggested we make videos of my learning process so that it can help others. So, stick around... if I can learn this stuff, you can too!
0:00 Intro, no bagel :(
1:00 What is Source Control?
2:13 Git vs GitHub
4:19 Ike Bio
5:26 Predecessors for context
7:48 Git basics
10:24 Q: do files have to be code?
16:32 the Git book
17:27 Branching and Merging
24:31 Wall time vs commit order
27:35 Moving along to GitHub
29:27 Exploring a GitHub
33:14 Pull Requests
37:13 Side Q: Please define shebang
41:03 Merge Conflict
42:16 Merging
43:25 Rebase explained
45:20 Back to the PR
46:10 Not just for complex projects
48:33 side Q: You mentioned sed
49:26 Conclusion
Thank you!
Enjoyed the episode! Have been using git since... well the beginning of git off and on and it's always good to hear someone explain it. Even if it's something you already know, you can pick out different ways of saying it or examples that help you explain it to others. Well done.
It was also a good reminder that old computer geezers like myself, that have been doing Unix since the early days have a vocabulary that is foreign to others haha.
On Unix machines time is kept as the number of seconds that has expired since Jan 1, 1970 at 00:00:00 UTC. That's great and gets everyone on the same page so what should we call our local time that we read from the clock on the wall? Wall time. In my current world of esoteric machines recording reams of data, our timestamps are in milliseconds since Jan 1, 1970 so I was just explaining this to someone at work curious about the column of huge numbers that accompanied the data they downloaded on a process.
In the Unix world we don't call this '#' a pound sign, that's too much to say, we call it a hash and we don't call this '!' an explanation point, who has time for that kind of verbiage!!
5:44 sccs, Source Code Control System. Ah, yes, sccs! You always remember your first version control system…