From 31d4699f65addfeda7c4bdbbef8de2a5ccde5f76 Mon Sep 17 00:00:00 2001 From: Xin LI Date: Wed, 28 Mar 2007 07:55:07 +0000 Subject: [PATCH] This commit was generated by cvs2svn to compensate for changes in r167981, which included commits to RCS files with non-trunk default branches. --- contrib/bzip2/Y2K_INFO | 34 ---------------------------------- 1 file changed, 34 deletions(-) delete mode 100644 contrib/bzip2/Y2K_INFO diff --git a/contrib/bzip2/Y2K_INFO b/contrib/bzip2/Y2K_INFO deleted file mode 100644 index 55fd56a2edbf..000000000000 --- a/contrib/bzip2/Y2K_INFO +++ /dev/null @@ -1,34 +0,0 @@ - -Y2K status of bzip2 and libbzip2, versions 0.1, 0.9.0 and 0.9.5 -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Informally speaking: - bzip2 is a compression program built on top of libbzip2, - a library which does the real work of compression and - decompression. As far as I am aware, libbzip2 does not have - any date-related code at all. - - bzip2 itself copies dates from source to destination files - when compressing or decompressing, using the 'stat' and 'utime' - UNIX system calls. It doesn't examine, manipulate or store the - dates in any way. So as far as I can see, there shouldn't be any - problem with bzip2 providing 'stat' and 'utime' work correctly - on your system. - - On non-unix platforms (those for which BZ_UNIX in bzip2.c is - not set to 1), bzip2 doesn't even do the date copying. - - Overall, informally speaking, I don't think bzip2 or libbzip2 - have a Y2K problem. - -Formally speaking: - I am not prepared to offer you any assurance whatsoever - regarding Y2K issues in my software. You alone assume the - entire risk of using the software. The disclaimer of liability - in the LICENSE file in the bzip2 source distribution continues - to apply on this issue as with every other issue pertaining - to the software. - -Julian Seward -Cambridge, UK -25 August 1999