Git is one of my favorite tools of all times. Not only has it been a time and life saver in my coding projects, it has also helped me out in other aspects - ke

Git is one of my favorite tools of all times. Not only has it been a time and life saver in my coding projects, it has also helped me out in other aspects - keeping versions of documents. Once, at work, I created a script that would take regular git 'snapshots' of all the procedures defined on a SQL Server. O'course, there could have been better code management and deployment practices in the first place, but this script let me introduce some sanity without affecting the DBAs workflows. Off-late, I have been working on a pure python implementation of Git (Calling it Pigit [1]). While, I am attempting to clone git's behavior in Python, I believe there are important lessons to be learned about the different components involved. I am also attempting to see if I can make it modular enough to have changeable 'reference' or 'object' store (instead of the file system). One use-case I can think of, off the top-of-my-head, is having an entirely in-memory repository for testing scripts or purely for pedagogical reasons. Strangely, I never thought of looking into the AOSA Book for Git! Thanks for the reference :) [1] https://github.com/rajatkhanduja/pigit https://github.com/rajatkhanduja/pigit