title: Managing PDFs/binaries with Git or other VCS
body: <p>I'm working on a LaTeX project at the moment for a "thesis" of sorts, and I figured it would be a safe idea to track the work-in-progress with Git, as it's probably the nicest version-control system I've come across. Now, Git will handle source code files brilliantly, but how well does it handle binary files? </p>
  
  <p>I'm unsure as to whether to track my generated PDFs as well as the *.tex sources. Even though I can regenerate my PDFs from any revision/branch, this can be time-consuming, and it's usually quicker to just bring up the relevant PDF version; will Git handle this? Is there a way to flag explicit versions within a Git repository, and can I set it up so, for example, I can quickly compare the PDF output of today's version with last week's? </p>
  
  <p>Rolling back to a specific branch will overwrite the PDFs, or at the very least, require a recompile; I just want to be able to log my progress and efficiently store it, and in the process be able to back up my work. Git might be my solution, but are there better ones?</p>
  
  <p><strong>EDIT</strong> My brother sent me a link to some documentation on <a href="http://progit.org/book/ch2-6.html" rel="nofollow">tagging</a>, so that solves the versioning part of my question.</p>