https://inmachineswetrust.com/enSun, 23 Aug 2020 20:35:34 GMTNikola (getnikola.com)http://blogs.law.harvard.edu/tech/rsshttps://inmachineswetrust.com/posts/git-deep-dive-checkout/Red Huq<div><style type="text/css"> div.prompt { display: none; } div.rendered_html table, .rendered_html th, .rendered_html tr, .rendered_html td { font-size: 16px; border: 1px solid black; } </style> <div class="cell border-box-sizing text_cell rendered"><div class="prompt input_prompt"> </div><div class="inner_cell"> <div class="text_cell_render border-box-sizing rendered_html"> <p>I love git. I think it's a brilliant masterpiece of design and programming by Linus Torvalds. To me it's more than just a tool—it's art. Ok I'm a little weird but we know that today git is the de facto tool for version control and an unequivocal cornerstone of successful software development.</p> <p>In this blog post series, I'm going to dive <em>really</em> deep into the inner workings of the commands <code>git checkout</code> and <code>git reset</code>, break them down logically, and expose the method to the madness. You might already be familiar with a few aspects of these commands, but both of them conceal surprisingly powerful and useful functionality. Some of it might be new territory but I hope a lot of it will absolutely blow your mind. Either way, let's started with <code>git checkout</code>.</p> <p><a href="https://inmachineswetrust.com/posts/git-deep-dive-checkout/">Read more…</a> (13 min remaining to read)</p></div></div></div></div>gitsoftware developmentversion controlhttps://inmachineswetrust.com/posts/git-deep-dive-checkout/Sat, 20 Jun 2020 14:00:00 GMT