Manage PDF files / executables using Git or another VCS

Question

I am currently working on a LaTeX abstract project, and I decided that it would be a safe way to track work in progress using Git, as this is probably the most beautiful version of the monitoring system I came across. Git will now process source files brilliantly, but how well does it handle binary files?

I am not sure whether to track my generated PDF files, as well as * .tex sources. Despite the fact that I can regenerate my PDF files from any edition / branch, this can take a lot of time, and, as a rule, it is faster to simply raise the corresponding version of the PDF; will git handle this? Is there a way to flag explicit versions in the Git repository, and can I customize it, for example, can I quickly compare the output of the PDF version of today's version with last week?

Returning to a specific branch overwrites the PDF files or, at least, requires recompilation; I just want to be able to record my progress and store it efficiently, and in the process there will be the ability to back up my work. Git may be my solution, but are there any better ones?

EDIT My brother sent me a link to some documentation on tagging , so that solves the version control part of my question.

Answer 1

I think the best solution will depend on how you are going to use VCS. If you often make a distinction between PDF files, git is probably not a great solution.

diff LaTeX, PDF, git, , . , , - "bisect", . Bisect , . bzr, , bzr, . , , .

. PDF , . PDF ? , makefile ?