Good idea, I add a shellscript for that. Reasons to keep the html and pdf versions in git:
1. want to show how the Pandoc created PDF and HTML versions look like 2. As this is a specification, we do need a frozen document per released version. PDF for offline usage, HTML for online display. As soon as we find a way to keep revisions of GH pages, we can use that for the HTML version and link to the PDF version for download. Robert Am 10.01.2014 um 13:29 schrieb Misagh Moayyed <[email protected]>: > Robert, > Apologies if this has already been discussed before. Is there a particular > reason we are keeping track of html/pdf versions of the doc in the repo? PDFs > are specially hard to merge. It might also make sense to create a small > shell script to invoke pandoc commands to generate html/pdf versions on the > fly. > > Misagh > > > From: "Robert Oschwald" <[email protected]> > To: [email protected] > Sent: Wednesday, January 8, 2014 9:55:59 PM > Subject: [cas-dev] Merge pull #355 > > I plan to merge #355 tomorrow, 05pm MET. > > Robert > > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
