Replies: 1 comment
-
|
From: rc***@kn*** (Ryan Challener) I think it's best that the user can get all they need from one command, rather than requiring them to download from multiple locations. Is there a way to specify that a file not be included in the history? If not then maybe we do need to put the documents elsewhere. I suspect we will also run into this with the figures in the documents, especially since I've included both the .png and .odg files for each figure, so that future contributors can make changes to them. -Ryan From: BART-devel <ba***@ph***> on behalf of AJ Foster <aj***@kn***> Hi everyone, Every time the Transit user manual or code manual is compiled (into a PDF), Git stores the entire file in its history. This is fine, but over time the history will start to get very large because it includes the entire file, instead of just the changes that were made to it. I would recommend that we do not include the compiled PDFs in the source, but rather put them on planets.ucf.edu (somewhere that makes sense) and link to them in the README. Thoughts?
BART-devel mailing list |
Beta Was this translation helpful? Give feedback.
-
The following is an archived message from the BART-devel mailing list, which has now closed.
From: aj***@kn*** (AJ Foster)
Date: Sat, 11 Jul 2015 02:30:13 +0000
Subject: [BART-devel] Compiled LaTeX
Hi everyone,
Every time the Transit user manual or code manual is compiled (into a PDF), Git stores the entire file in its history. This is fine, but over time the history will start to get very large because it includes the entire file, instead of just the changes that were made to it.
I would recommend that we do not include the compiled PDFs in the source, but rather put them on planets.ucf.edu (somewhere that makes sense) and link to them in the README.
Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions