The only loss is the ability to look at changes over time. If that's an important feature, you could write the files with a commit hash in the name. But that may not be worth it.
On Tue, Mar 14, 2017 at 4:38 AM, Simon Peyton Jones via ghc-devs < [email protected]> wrote: > It's very helpful to have a live, up to date PDF. Not everyone has OTT, > which is required to make it. And OTT isn't available on Windows at all :-( > > Simon > > | -----Original Message----- > | From: ghc-devs [mailto:[email protected]] On Behalf Of Phil > | Ruffwind > | Sent: 14 March 2017 00:14 > | To: [email protected] > | Subject: Re: Removing core-spec.pdf from repository? > | > | > I also dislike generated files in repos, but would like to point out > | > that there are a few pages out there that reference the link > | > https://github.com/ghc/ghc/blob/master/docs/core-spec/core-spec.pdf > | > directly; these would brake. But there is probably nothing we can > | > easily do about that. > | > | Could replace it with a plain text file that says: "MOVED to > | https://XXX"; > | The build system could then be tweaked to output the .pdf somewhere > | else so it would not overwrite this dummy file. > | _______________________________________________ > | ghc-devs mailing list > | [email protected] > | http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > _______________________________________________ > ghc-devs mailing list > [email protected] > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs >
_______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
