Skip to content

Keep thread pools documentation separate #214

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

Merged
merged 1 commit into from
Dec 29, 2014

Conversation

pitr-ch
Copy link
Member

@pitr-ch pitr-ch commented Dec 28, 2014

followup of #213
cc @jdantonio @jrochkind

@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling 80c5495 on pitr-ch:master into a7acb85 on ruby-concurrency:master.

@pitr-ch
Copy link
Member Author

pitr-ch commented Dec 28, 2014

@jrochkind moving the thread_pools.md file from the inclusion to being stand-alone. I agree it makes more sense.

@jrochkind I agree it would be nice to make links also work on github. It would have to be easy to maintain though.

Which brings me to the question of separated .md files in doc directory. As Jerry mentioned they are easier to edit and maintain (I agree) so It's better to keep the files there, we are already struggling with documentation completeness and up-to-dateness so I think we should also be thinking about making it easy for us.

jdantonio added a commit that referenced this pull request Dec 29, 2014
Keep thread pools documentation separate
@jdantonio jdantonio merged commit 8e921c6 into ruby-concurrency:master Dec 29, 2014
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.

3 participants