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

Remove circleci, old freebsd ci and vagrant (pkgeval) config files #31841

Merged
merged 3 commits into from
Apr 26, 2019

Conversation

ViralBShah
Copy link
Member

With the various recent upgrades to our infrastructure, we no longer use circleci, the old freebsd ci and vagrant (which was used for the old pkgeval).

@staticfloat Is it ok to delete the files in this PR?

@ViralBShah
Copy link
Member Author

ViralBShah commented Apr 26, 2019

Can we also delete contrib/ackrc and its README? If people use it, we should move them to contrib/ack.

@staticfloat
Copy link
Sponsor Member

Can we also delete contrib/ackrc and its README? If people use it, we should move them to contrib/ack.

I would just move them now. I'm not sure how useful they are, but this is why we have a contrib/ directory.

@musm
Copy link
Contributor

musm commented Apr 26, 2019

@ViralBShah you will also need to remove the section https://github.com/JuliaLang/julia/blob/master/README.md#vagrant

@ViralBShah
Copy link
Member Author

I think the README itself needs refactoring. I will take a crack at it.

@musm
Copy link
Contributor

musm commented Apr 26, 2019

Sounds good, but maybe in another PR ?

@ararslan ararslan merged commit 2d8c1ec into master Apr 26, 2019
@ararslan ararslan deleted the vs/deletion branch April 26, 2019 19:11
@ViralBShah
Copy link
Member Author

I was planning to do it in this PR, but now that this is merged, @musm do you want to submit the PR? Otherwise I will get to it on sunday.

@StefanKarpinski
Copy link
Sponsor Member

I think the README itself needs refactoring.

It's pretty long. I wonder if it wouldn't be better to give a very high-level list of references to other locations where more detailed documentation of how to do various things can be found.

@ararslan
Copy link
Member

I was planning to do it in this PR

My bad, didn't realize that was your intention.

@ViralBShah
Copy link
Member Author

ViralBShah commented Apr 29, 2019

No worries. Now in #31858

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

Successfully merging this pull request may close these issues.

None yet

5 participants