From: Stefan Naewe <stefan.naewe@atlas-elektronik.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Paul Menzel <paulepanter@users.sourceforge.net>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: use case: keep the output of a markup (TeX) file under revision control
Date: Thu, 17 Feb 2011 13:27:01 +0100 [thread overview]
Message-ID: <4D5D1415.7080405@atlas-elektronik.com> (raw)
In-Reply-To: <m362si97n4.fsf@localhost.localdomain>
On 2/17/2011 1:19 PM, Jakub Narebski wrote:
> 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.
prev parent reply other threads:[~2011-02-17 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 10:37 use case: keep the output of a markup (TeX) file under revision control Paul Menzel
2011-02-17 12:03 ` Stefan Naewe
2011-02-17 19:51 ` Paul Menzel
2011-02-18 6:59 ` Stefan Naewe
2011-02-17 12:19 ` Jakub Narebski
2011-02-17 12:27 ` Stefan Naewe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D5D1415.7080405@atlas-elektronik.com \
--to=stefan.naewe@atlas-elektronik.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=paulepanter@users.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).