summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMike McGreevy <mamcgree@hdfgroup.org>2010-05-14 18:47:21 (GMT)
committerMike McGreevy <mamcgree@hdfgroup.org>2010-05-14 18:47:21 (GMT)
commit912e7b99ee3b6f6455e02aba93c1563ebe4ae944 (patch)
treee814ade3d6047044cc28c15ebdccaac0f3182d14
parent453a3910ab7942daa7b01e821e15853cb7a0ba23 (diff)
downloadhdf5-912e7b99ee3b6f6455e02aba93c1563ebe4ae944.zip
hdf5-912e7b99ee3b6f6455e02aba93c1563ebe4ae944.tar.gz
hdf5-912e7b99ee3b6f6455e02aba93c1563ebe4ae944.tar.bz2
[svn-r18806] Purpose:
Update RELEASE.txt Description: Remove outdated known issue (should have been removed from 1.8.4, whoops) from RELEASE.txt Tested: doc only, none needed.
-rw-r--r--release_docs/RELEASE.txt6
1 files changed, 0 insertions, 6 deletions
diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt
index a12b8a9..adfcb30 100644
--- a/release_docs/RELEASE.txt
+++ b/release_docs/RELEASE.txt
@@ -409,12 +409,6 @@ Known Problems
collective abort of all ranks at t_posix_compliant / allwrite_allread_blocks
with MPI IO. CMC - 2009/04/28
-* There is a known issue in which HDF5 will change the timestamp on a file
- simply by opening it with read/write permissions, even if the file is not
- modified in any way. This is due to the way in which HDF5 manages the file
- superblock. A fix is currently underway and should be included in the 1.8.4
- release of HDF5. MAM - 2009/04/28
-
* For gcc v4.3 and v4.4, with production mode, if -O3 is used, H5Tinit.c
would fail to compile. Actually bad H5Tinit.c is produced. If -O (same
as -O1) is used, H5Tinit.c compiled okay but test/dt_arith would fail.