Merge remote-tracking branch 'upstream/master'
Merge branch 'master' of https://github.com/chapel-lang/chapel
Adding note for specifying stdin file in execopts
Initial draft of sets README
Initial draft of lsq readme
Merge branch 'master' of https://github.com/chapel-lang/chapel into cygwin-numcores
Add missing READMEs to list of READMEs.

We were missing references to README.knc, README.curl, README.auxIO
Merge branch 'master' into docFreezeReleaseREADME
Hadn't seen that README.knc had moved.  Updating its location.
Merge branch 'master' of github.com:chapel-lang/chapel into docs-lsq-readme
Adding an entry to release/README
Make Knights Corner description match the style of the others
Merge branch 'master' of github.com:chapel-lang/chapel into docs-sets-readme
Adding an entry to release/README
Adding cygwin to the list of platforms that use /proc/cpuinfo

Cygwin has a /proc/cpuinfo, so should use the same rule as other
platforms.  Unfortunately, it doesn't have a 'siblings' entry
(at least for my laptop), so it doesn't work.  We may have better
luck on the official test platform.  In any case, this is a
step in the right direction.

I've proposed to Greg that we should make the default case
optimistically use /proc/cpuinfo rather than making it an
error case so that other platforms that support /proc/cpuinfo
will work without human intervention (and if they don't work,
a similar amount of developer intervention is required as if
it gets a cleaner error message).
Merge pull request #480 from lydia-duncan/docFreezeReleaseREADME

Add missing READMEs to list of READMEs [reviewed by Sung and Brad]

We were missing references to README.knc, README.curl, README.auxIO
Formatting changes
Merge pull request #466 from benharsh/docs-stdin

Adding note for specifying stdin file in execopts
Adding a reference to the dist primer; minor style changes
Merge pull request #481 from bradcray/cygwin-numcores

Adding cygwin to the list of platforms that use /proc/cpuinfo for this test

Cygwin has a /proc/cpuinfo, so should use the same rule as other
platforms.  Unfortunately, it doesn't have a 'siblings' entry
(at least for my laptop), so it doesn't work.  We may have better
luck on the official test platform.  In any case, this is a
step in the right direction.

I've proposed to Greg that we should make the default case
optimistically use /proc/cpuinfo rather than making it an
error case so that other platforms that support /proc/cpuinfo
will work without human intervention (and if they don't work,
a similar amount of developer intervention is required as if
it gets a cleaner error message).