Merge pull request #150 in HDFFV/hdf5 from ~BMRIBLER/hdf5_1_8_18_bmr:hdf5_1_8_18 to hdf5_1_8_18

Replaced an incorrect work-around note with information about future feature to fix the problem.

* commit 'a9aa43c8c23754cf4f3fb719463773ee38aeb3b6':
  Description:     Replaced an incorrect work-around note with info about future feature     to fix the problem.

1 files changed, 3 insertions, 15 deletions

diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt
index 234a523..3c23fc2 100644
--- a/release_docs/RELEASE.txt
+++ b/release_docs/RELEASE.txt
@@ -264,7 +264,7 @@ Bug Fixes since HDF5-1.8.17
     High-Level APIs:
     ---------------
 
-    - The high-level Packet Table (PT) API did not write data correctly when
+    - The high-level API Packet Table (PT) did not write data correctly when
       the datatype is a compound type that has string type as one of the
       members.  This problem started in 1.8.15, after the fix of HDFFV-9042
       was applied, which caused the Packet Table to use native type to access
@@ -274,8 +274,8 @@ Bug Fixes since HDF5-1.8.17
       user's provided datatype during creation or the packet table's datatype
       during opening.  If an application wishes to use native type to read the
       data, then the application will request that.  However, the Packet Table
-      doesn't provide a way to specify memory datatype in this release.
-      Please refer to the Known Problems section for a work-around.
+      doesn't provide a way to specify memory datatype in this release.  This
+      feature will be available in future releases, HDFFV-10023.
 
       (BMR, 2016/10/27, HDFFV-9758)
 
@@ -445,18 +445,6 @@ The following platforms are not supported but have been tested for this release.
 
 Known Problems
 ==============
-* Currently, the Packet Table doesn't provide a way to specify memory datatype
-  when the packet table is read.  To work around this limitation, an
-  application can use the following approach:
-  + For the C API of the Packet Table
-    - call the PT API H5PTget_type to get the datatype of the packet table
-    - call the C API H5Tget_native_type to get the native type of that datatype
-  + For the C++ API of the Packet Table
-    - call the member function PacketTable::GetDatatype to get the datatype
-      of the packet table
-    - call the C API H5Tget_native_type to get the native type of that datatype
-  (BMR, 2016/10/27, HDFFV-9758)
-
 * On windows platforms in debug configurations, the VFD flush1 tests will fail
   with the split and multi VFD drivers. These tests will display a modal debug
   dialog which must be answered or wait for the test timeout to expire.