Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

document the archive --large flag #330

Merged
merged 1 commit into from
Dec 25, 2018

Conversation

anarcat
Copy link
Contributor

@anarcat anarcat commented Sep 26, 2018

It's in the source but not in the docs.

It's in the source but not in the docs.
Copy link
Contributor

@JustAnotherArchivist JustAnotherArchivist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks.

I wonder whether we want to keep this option at all. It's not being used nowadays (last use was over a year ago!), pipeline operators to my knowledge often don't set the LARGE variable anyway, and most current pipelines are big enough to deal with fairly large jobs. It seems that this option is no longer necessary.

But that's something for a separate issue. Documenting the existing option is good regardless! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants