diff options
authorXin LI <delphij@FreeBSD.org>2007-03-28 07:55:07 +0000
committerXin LI <delphij@FreeBSD.org>2007-03-28 07:55:07 +0000
commit4446b1794f2c3e302d9897f1f8b0f236aeb96183 (patch)
parent1b79bae0f8e284925df36d28ffc921bda57a7c61 (diff)
Remove Y2K_INFO which does not belong to this distribution
Notes: svn path=/vendor/bzip2/dist/; revision=167981
1 files changed, 0 insertions, 34 deletions
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