/explore
|
You are here 
|
initialcommit.com | ||
| | | | |
kennyballou.com
|
|
| | | | | A backwards introduction to the information manager from hell | |
| | | | |
blog.foletta.net
|
|
| | | | | [AI summary] This technical article explores the internal data structures and fundamental constructs of Git, explaining how it manages source control through blobs, trees, commits, branches, and the index. | |
| | | | |
chambers.io
|
|
| | | | | So far this week we've talked about what Git is and how to use it. If you're anything like me, you want to know how things work under the hood. When you first learn Git it can seem like magic...but it also seems like something that can easily break. Or something that works by pure demonic byte voodoo. One of the best things Git does is allow you to write code with confidence - fear not about breaking things or losing files. They're always recoverable. To feel confident, it helps to know how things work. | |
| | | | |
it-notes.dragas.net
|
|
| | | |||
