From: Paul Menzel <paulepanter@users.sourceforge.net>
To: git@vger.kernel.org
Subject: use case: keep the output of a markup (TeX) file under revision control
Date: Thu, 17 Feb 2011 11:37:00 +0100 [thread overview]
Message-ID: <1297939020.3959.12.camel@mattotaupa> (raw)
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2011-02-17 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 10:37 Paul Menzel [this message]
2011-02-17 12:03 ` use case: keep the output of a markup (TeX) file under revision control 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
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=1297939020.3959.12.camel@mattotaupa \
--to=paulepanter@users.sourceforge.net \
--cc=git@vger.kernel.org \
/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).