Fix description of NCF-29 change
Merge branch 'master' of http://github.com/Unidata/netcdf-c

Updating to 4.3.1-rc1
Merge branch 'master' of http://github.com/Unidata/netcdf-c
Minor cleanups to reduce warnings in headers, and switch from MPI_BYTE to MPI_INT
for MPI_Allreduce() call.
Added new option to enable/disable 'Data Conversion warnings', ENABLE_CONVERSION_WARNINGS, when using CMake-based builds.
Added a custom cmake test configuration file to override the default '50' warnings when submitting to a remote dashboard.
Updated Building-with-CMake file.
Fix some cmake syntax errors
Increased timeout for large file tests.
Merge branch 'cmake' of https://github.com/opoplawski/netcdf-c into opoplawski-cmake
Fixed Jira number in entry.
Merge branch 'master' of http://github.com/Unidata/netcdf-c before
making patch.
Updated RELEASE_NOTES.md with issues addressed by Quincy K.
Reduced default warning number to accomodate bandwidth limitations on hosted CDash.
Merge branch 'master' of https://github.com/Unidata/netcdf-c
Quincey's patch for NCF-269 parallel I/O bug.
Add release notes entry.
Added error messages when compiling hdf4 support but no hdf4 libraries are present.
Merge branch 'master' of http://github.com/Unidata/netcdf-c
Added NC_USE_STATIC_CRT option to Cmake-based builds.
[NCF-265]
Ncgen is unable to resolve
ambiguous references to an enum
constant when two different enums
have same econstant name.

Solved by allowing more specific
forms for econstant references.
1. /.../enumname.enumconstname
2. enumname.enumconstname
3. enumconstname

Case 1 is resolved by using the econstant
in the specific enum definition. If none is
found, an error is reported.

Case 2 is resolved by
1. finding an enclosing group with an
   enum definition with the specified name
   and containing the specified econstant.
   If there are more than one, then an error is reported
2. finding all enum definitions in the dataset that have
   the specified enum name and contain the specified
   econstant. If more than one is found, then an error is reported.
If the above two methods fail, then report an error.

Case 3 is similar to case 2, but all enums, irrespective
of name are used if they contains the specified enum constant.

The ref_tst_econst.cdl test in ncdump is causing ncdump
to fail. So there may be yet some problem.
[NCF-265]
Ncgen is unable to resolve
ambiguous references to an enum
constant when two different enums
have same econstant name.

Solved by allowing more specific
forms for econstant references.
1. /.../enumname.enumconstname
2. enumname.enumconstname
3. enumconstname

Case 1 is resolved by using the econstant
in the specific enum definition. If none is
found, an error is reported.

Case 2 is resolved by
1. finding an enclosing group with an
   enum definition with the specified name
   and containing the specified econstant.
   If there are more than one, then an error is reported
2. finding all enum definitions in the dataset that have
   the specified enum name and contain the specified
   econstant. If more than one is found, then an error is reported.
If the above two methods fail, then report an error.

Case 3 is similar to case 2, but all enums, irrespective
of name are used if they contains the specified enum constant.

The ref_tst_econst.cdl test in ncdump is causing ncdump
to fail. So there may be yet some problem.