Adding manual to .gitignore?

[betanalpha]

I recall that doc/stan-reference-2.0.1.pdf was going to be added to the .gitignore file? Right now anytime the manual gets built locally it adds additional steps before changing branches/fast-forwarding.

[mbrubake]

Instead of having the PDF in develop, we could just have it live in release
branches.

On Mon, Nov 11, 2013 at 4:49 PM, Michael Betancourt <
notifications@github.com> wrote:

I recall that doc/stan-reference-2.0.1.pdf was going to be added to the
.gitignore file? Right now anytime the manual gets built locally it adds
additional steps before changing branches/fast-forwarding.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/381
.

[bob-carpenter]

This is an ugly situation all around.

The reason it's checked in is so that we can use Git's built-in
download buttons, that just bundle the source together. That
way we don't have to build our own distribution tarball because
it's just a snapshot of a repository.

If we only have it live in release branches, then we have the
hassle of removing it from develop and then adding it back into
release. I'd be OK with that.

• Bob

On 11/11/13, 4:58 PM, Marcus Brubaker wrote:

Instead of having the PDF in develop, we could just have it live in release
branches.

On Mon, Nov 11, 2013 at 4:49 PM, Michael Betancourt <
notifications@github.com> wrote:

I recall that doc/stan-reference-2.0.1.pdf was going to be added to the
.gitignore file? Right now anytime the manual gets built locally it adds
additional steps before changing branches/fast-forwarding.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/381
.

—
Reply to this email directly or view it on GitHub #381 (comment).