<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>Kill it! That's terrible practice indeed. Speaking of generated files, it's time to check if our Unicode tables are up to date.</div><div><br></div><div><br></div><div><br></div><div id="composer_signature"><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><div style="font-size:85%;color:#575757">David Feuer</div><div style="font-size:85%;color:#575757">Well-Typed, LLP</div></div><div><br></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Ben Gamari <ben@well-typed.com> </div><div>Date: 3/13/17 6:57 PM (GMT-05:00) </div><div>To: GHC developers <ghc-devs@haskell.org> </div><div>Subject: Removing core-spec.pdf from repository? </div><div><br></div></div>Hello everyone,<br><br>Currently there is a typeset copy of the Core specification in the GHC<br>repository. This means any time someone changes the specification the<br>repository grows by around 300kB. While this isn't the end of the<br>world, it's generally considered bad form to put generated files under<br>version control.<br><br>Of course, the tools required to typeset the specification (ott and<br>LaTeX) are non-trivial to install, so there is considerable convenience<br>that comes from having a typeset version readily available.<br><br>I suggest that we remove the PDF from the repository but instead I can<br>start including it in my nightly documentation builds. Any objections?<br><br>Cheers,<br><br>- Ben<br></body></html>