Time to read: 1 minutes.
Git has been the dominant source code control program since 2008. When on assignment as a software expert for a US federal court case, I always request entire git repositories instead of just the source code at one specific historical date. Having the entire git repository means that I can learn how a project was built, and who did what.
High Level (‘Porcelain’) Git CLI
2023-03-30 Partial Clone of Upstream 2023-03-12 The Git Pager 2023-03-11 The First Git Branch Is Created Lazily 2023-05-26 Replicating a Git Directory Tree 2020-12-21 Propagating Git Template Changes Downstream 2011-08-18 Working With Bug Fix and Feature Branches in Git 2023-03-11 Updating a Tree of Git Repositories 2022-05-05 How Much Do You Actually Program?
Low Level (‘Plumbing Internals’) Git CLI
2023-04-25 Git Concepts 2023-05-15 Low Level Git Commands (‘Plumbing Internals’)
2023-03-23 Introduction to libgit2 2023-05-11 Working With Git Repos Using Ruby's Rugged Gem 2023-05-10 Git/Libgit2 Notes
2023-05-15 Divergent Libgit2 Library Wrappers 2023-05-15 Merge and Pull: Git CLI vs. Libgit2 Wrappers
© Copyright 1994-2023 Michael Slinn. All rights reserved.
For requests to use this copyright-protected work in any manner, email email@example.com.