3 ms·
Yes I don't know how anyone can come to the conclusion that the CLI isn't by far the biggest problem. It is terrible. The other big issue is that people tell y
by IshKebab 3y ago
Yes I don't know how anyone can come to the conclusion that the CLI isn't by far the biggest problem. It is terrible.
The other big issue is that people tell you not to use a GUI, and there are a lot of GUIs that are not very good. Using a good GUI (I recommend GitExtensions, GitX on Mac or Git Graph in VSCode) makes Git waaaay easier to understand because the model is literally drawn for you.
Find me a Git tutorial with no diagrams and I will change my mind.
Also the author's "these are core facts about Git" list is not very accurate so I'm not sure how much they really understand it. A commit is not a snapshot and a patch. It is literally only a snapshot.
Edit: I actually searched Git tutorials and there are a surprising number of terrible Git tutorials with no diagrams! Though I guess I shouldn't be surprised about the official Git tutorial and W3Schools.
- bornfreddy 3y ago> A commit is not a snapshot and a patch. It is literally only a snapshot. When you do cherry-pick, you supply a commit id, but actually a patch (diff between the commit and its parent) is applied. So yes, commit (/id) can mean a patch in some cases.
- IshKebab 3y agoNo. The operation involves diffing snapshots to make a patch and then applying that patch. But a commit is still only ever a snapshot. Like, is an ordinary file a patch? No of course not. But you can still turn it into a patch by diffing two files. In the same way a commit is just a set of files. But you can turn it into a patch by diffing two commits. > commit (/id) can mean a patch in some cases. It doesn't. It means "which snapshot would you like me to turn into a patch by diffing with its parent snapshot?"