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

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

From
Stefan Naewe <stefan.naewe@atlas-elektronik.com>
Date
Feb 17, 2011, 12:27 UTC
Message-ID
<4D5D1415.7080405@atlas-elektronik.com>
In-Reply-To
<m362si97n4.fsf@localhost.localdomain>
On 2/17/2011 1:19 PM, Jakub Narebski wrote:
Show 11 quoted lines
> Paul Menzel <paulepanter@users.sourceforge.net> writes:
> 
> 1. Mark PDF files as binary, if they are not already considered binary.
> 
> 2. Create custom merge driver for PDF files, which would compile
>    source *.tex file to PDF, provided that TeX is installed, and that
>    source file itself is not in merge conflict
> 
> 3. Creating pre-commit hook would ensure that you have refershed PDF
>    files during ordinary commit.  Note that this hook is not always ran
>    (you can force running it with --verify option to git-commit).
??

I only see '--no-verify' in 'git help commit' to bybass the 'pre-commit' hook but not the other way round.

Puzzled,
  Stefan
-- 
----------------------------------------------------------------
/dev/random says: Beam me up Scotty. This isn't the men's room.
Previous: Jakub Narebski
Message 6 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.