Hi Ken, Ken Mankoff writes:
> I'd like to keep derivative products (the LaTeX output, the final PDF, > etc.) available in Git, but not commit those changes each time I > change the Org file. Perhaps git-annex as appropriate for this, but > seems over-kill. > > Is there some way to mostly-seamlessly commit the LaTeX and/or PDF > and/or other files to their own git branches but in a way that > overwrites the history of that branch, so that a small Org file that > generates a big binary PDF does not pollute the git tree? There are probably better solutions, but maybe this could help you: use org-publish (which also works when the output is LaTeX/PDF, and not only with HTML). See https://orgmode.org/manual/Publishing.html You should have to define a new publishing project and declare a directory for the PDFs derivatives, applying a value to :publishing-directory, and configure in this directory a second git repository, only for PDFs. The value of :publishing-function keyword should be `org-latex-publish-to-pdf'. Best regards, Juan Manuel
