Відео

This is truly some of the best technical content on YT. Everything: the actual info content, the diagrams and animations, the effort put into pre-prod with good, simple, yet rich examples. Really nice one. I have only one piece of feedback on what can be improved: the ads (for me at least) are so frequent I keep losing my place mentally. I’ve actually never seen a yt video with such frequent ads. Hey if they’re paying your bills: worth it. Just something to know

kol hakavod! these series of yours achi is completely brilliant!

Hi bro did u covered all the topics related to networking??? I want to prepare for next year exam so this year there was a question like switch works in which mode ans is promiscuous so i want to know have u covered everything related to networking subject???

I could probably get by my entire life without rebasing, but thanks for the video! I find very strange that the rebase argument have a completely different meaning depending on the options, like --onto. Options should ideally only some minor aspect of how a command is carried out, not completely change the meaning of the arguments. It confuses me...

Great video! :D ✨

As usual, a really helpful lecture! I learned a lot!👏👏👏

welcome back ! put a video for git-tags and git graph

great explanation, amazing visualization of the concept thank you for your work

No, no no.... Why do you suddenly start to overlay everything you say in big letters like an american tv commercial? It only distracts from what you're trying to teach. You were doing these videos so well before, so please, don't do that. It's really annoying!

This is by far the best deep-dive videos on git. Precise, to the point, brilliant! Thank you. Please keep making such amazing videos, I have my notifications on :)

Amazing! Most tutorials just talk about commits and often omits showing what happens in the working tree and the index. This is exactly the tutorial I was missing to understand the whole picture. Many thanks for putting together this great video!

Question: In the diagram at 27:13 how can the second commit contain the full state of our files it it only references the tree object pointing to the second file we created? Shouldn't the tree object it references point to both our files (blobs) at this stage? Or did I miss something? 🙂

Wow! Already, after just 4 videos, this is turning out to be the best series of videos explaining git that I've seen to far! Great job!! 🙂

wow

I love you dude

love this!

Very useful

Always so good, best I have ever met for git video series

Great explanation. Thank you very much ❤

omg you are back! Love your videos

These are great, kind of deep knowledge that is surprisingly good. Thank you very much. I have a question, at the end, 24:35, git commit-tree 8abe3..., what is this created tree exactly? does it contains only Blob 2932B TEXT.TXT? or should it also contain other blob in the directory? (BRIEF.TXT)

For the problem at 18:50 I solved it this way: git branch new_feature git update-ref refs/heads/main <old commit for main> Is there any drawback doing it this way ? Now that I think about it, I don't see any difference between "git reset --soft" and "git update-ref" other than the fact that "git reset" lets you use relative commits like HEAD~N Thanks.

Fantastic explanation.👆

Best channel to cover git internals

Amazing video and analysis of the subjects. I can't thank you enough for such a high quality content made available for free.

Thanks!

Reqlly useful videos!!!

Hey, at around 7:20 your git status says nothing to commit but I am not able to initialize a git repo :( PS D:\test-git> tree /f Folder PATH listing for volume New Volume Volume serial number is E883-1978 D:. └───.git │ HEAD │ ├───objects └───refs └───heads PS D:\test-git> git status fatal: not a git repository (or any of the parent directories): .git PS D:\test-git> cat .git\HEAD ref: refs/heads/master

Great explanation. After seeing 3 videos I'm missing some info. 1. Do the sha files contain the content of the file? 2 How is the file tree, as seen by say an editor get created when I chechout a branch? 3 Does git go and recreate the entire tree from the blobs? 4 what if two files have the same sha? Thanks!!

Sir it is possible to make a commit in multiple branches ?? Like cherry pick , without cherry pick is there any other way to do the same??

my doubt is if you are creatina a pathch for a file called newfile.patch then you are doing a hard reset while you are doing hard reset it change the head what ever we want ,so that time patch file gets erased so how it able to take that patch file in to the current files and get added ??

Almost in tears watching this unfold.. so good. Will recommend to others

This is so good. . . Just stumbled upon your channel and was amazed how easy you explain with the visuals. Helped so much.

bro how to draw work graph using git commit hash teach how to fetch the hash and using that to create a work graph

Thank you. I need this. So far any website and or search I do asking what a frame in the data link layer is explains that is a frame is data that has been framed. That is a terrible explaination and no one is explaining it. From this video I at least know that it has something to do with simply adding more bits to the beginning and end of the data so as to identify the beginning and ending of the data (message).

Hi, I have a question. While re-ordering the base for the first commit of a branch in the tutorial - time : 22:15, you didn't checkout to the branch "new_branch" before applying "git rebase --onto". You applied it while you were in the main branch. But in the second case(time: 25:27) you checkout to the branch "feature_2" before proceeding with the "git rebase --onto". Can you help me on this please.

Man you are simply great. Thank you for taking your time and effort for generating such invaluable contents.

Excellent videos, thank you! I want to point out that at 19:20 in the video, a 'git reset --soft' would have worked just as well.

Finally I find a video that help understand this thing

All this example using rebase are valid when we don't have conflits, we just want rewrite the history, right? To deal with conflits merge still the better aproach, or am i wrong?

Valeu!

Damn, this is so good. Thank You Bro, I actually understood git under the hood !

Awesome thank you!

Thanks. Very useful! Much better than learning a bunch of commands that i don't understand!

Not Everyone Have This Like Of Deep Knowledge. Thanks For Publish For Free ❤.

YOU ARE FREAKIN AWESOME!

Thanks for the series

nice video! can you tell me the git command 'gg' alias for what ？

better than udemy. very good!

Very well structured and easy to follow guide, thank you