git/list[1] front-page[2] threads[3] people[4] search[5] about
 

use case: keep the output of a markup (TeX) file under revision control

From
PMPaul Menzel <paulepanter@users.sourceforge.net>
Date
Feb 17, 2011, 10:37 UTC
Message-ID
<1297939020.3959.12.camel@mattotaupa>
Dear Git folks,
(Please CC me when replying since I am not subscribed.)
I have the following use case and need an advise from you professionals.

A friend and I are writing a paper using TeX¹ and keep the files under revision control using Git. This works fine so far. But I want to also have the output (PDF) of the markup file under revision control to be able to access the PDF files even if for example no TeX installation is available on a system.

The problem now is, since the output is no plain text file, that merging/rebasing always shows conflicts which Git, of course, cannot solve.

Is there a way to set that up so that there are no conflicts? Would a pre-commit hook work which generates the PDF file prior to committing? And if no TeX installation is available it would just ignore the PDF files?

I could not find anything on the Web because having PDF as search string would just show up how to generate documentation about Git.

Thanks,
Paul
¹ Actually it is ConTeXt [1].
[1] http://wiki.contextgarden.net/Main_Page
Next: Stefan Naewe
Message 1 of 6 in “use case: keep the output of a markup (TeX) file under revision control”
  1. Paul MenzelFeb 17, 2011
  2. Stefan NaeweFeb 17, 2011
  3. Paul MenzelFeb 17, 2011
  4. Stefan NaeweFeb 18, 2011
  5. Jakub NarebskiFeb 17, 2011
  6. Stefan NaeweFeb 17, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.