John Blischak Avoid the use of tracking as a general term to avoid confusion.  over 8 years ago

Commit id: 9c52b373ac2bac74f907bb6dadca4cebca737321

deletions | additions      

       

Initialized empty Git repository in ~/thesis/.git/  \end{verbatim}  Now you are ready to start tracking versioning  your code (Figure \ref{fig:Fig1}). Conceptually, Git saves snapshots of the changes you make to your files whenever you instruct it to.  For instance, after you edit a script in your text editor, you save the updated script to your \verb|thesis| folder.  If you tell Git to save a shapshot of the updated document, then you will have a permanent record of the file in that exact version even if you make subsequent edits to the file. 

At this point, you have learned the commands needed to version your code with Git.  Thus you already have the benefits of being able to make edits to files without copying them first, to create a record of your changes with accompanying messages, and to revert to previous versions of the files if needed.  Now you will always be able to recreate past results that were generated with previous versions of the code (see the command \verb|git tag| for a method to facilitate finding specific past versions) and see the exact changes you have made over the course of a project.