diff --git a/BUGS b/BUGS
deleted file mode 100644
index 9126dd8c..00000000
--- a/BUGS
+++ /dev/null
@@ -1,79 +0,0 @@
-Except for many unimplemented things (listed in the TODO file), there may be
-true bugs too. If you experience any problems not listed here, do not hesitate
-to mail us (see http://www.lm-sensors.org/wiki/FeedbackAndSupport).
-But read this file and doc/FAQ first, please!
-
-============================================================================
-These are current problems with specific programs and drivers.
-In general, please don't send us mail telling us you have the
-same problem!!  Do send us mail if you have a fix!!
-
-
-================================
-Asus boards - as99127f support (w83781d driver)
-
-Several problems. Asus will not release a datasheet.
-Support was developed - and tweaked - with experimentation and user feedback.
-These will not be fixed unless we get a datasheet.
-If you have problems, please lobby Asus to release a datasheet.
-Unfortunately, several others have done so, without success.
-Please do not send mail to us asking for better as99127f support.
-We have done the best we can without a datasheet.
-The changes we do make to please some people generally makes
-things worse for people with other types of motherboard.
-Please do not send mail to the author or the sensors group asking for
-a datasheet or ideas on how to convince Asus.
-See doc/chips/w83781d for more information.
-
-================================
-i2c/smbus lockup (i2c-piix4 and i2c-ali15x3 drivers)
-
-Sometimes the i2c bus will get hung and the driver can't un-hang it.
-If this is caused by a hung sensor chip (mtp008 and w83781d chips may
-be culprits), only a reboot or even power cycle will clear it
-(if the SDRAM eeproms are on the hung i2c bus, the machine probably won't
-boot until the power is cycled).
-If there are bugs in the i2c bus drivers, or improvements we can make to
-error recovery, we don't know what they are.
-
-On the ASUS P5A motherboard, there are several reports that
-the SMBus will hang and this can only be resolved by
-powering off the computer. It appears to be worse when the board
-gets hot, for example under heavy CPU load, or in the summer.
-There may be electrical problems on this board.
-On the P5A, the W83781D sensor chip is on both the ISA and
-SMBus. Therefore the SMBus hangs can generally be avoided
-by accessing the W83781D on the ISA bus only.
-
-================================
-IBM Thinkpad laptops and sensors-detect
-See the file README.thinkpad
-
-
-================================
-mtp008 support
-
-This chip does not always respond, as evidenced by 'XX' fields
-in i2cdump. Results in non-detection by sensors-detect and/or
-the mtp008 driver, or periodic bad readings.
-Cause unknown - perhaps a bug in the chip, or the chip
-not meeting the i2c specifications.
-
-
-================================
-sis5595 (sis5595 and i2c-sis5595 drivers)
-
-These drivers latch on to many non-sis5595 chips which
-do not support sensors, i2c bus, or both.
-This is because SiS uses the same PCI ID for several different chips.
-This will have to be fixed by us to recognize these other chips.
-
-Right now, the driver tries
-writing the base addresses (using the force_addr=0x.... parameter to modprobe),
-it does not work for some machines (dmesg message is "force address failed").
-Either some chips do not support sensors, or there is some undocumented
-lock bit for the base address registers.
-
-Also, the temperature reading in sis5595 is usually wrong.
-Different formulas are required for different versions of
-the chip and different motherboards.
diff --git a/CHANGES b/CHANGES
index 8e7dcb58..8f900bcd 100644
--- a/CHANGES
+++ b/CHANGES
@@ -2,6 +2,7 @@ lm_sensors CHANGES file
 -----------------------
 
 SVN HEAD
+  File BUGS: Delete
   File i2c-dev.h: Support I2C block reads with specified length
   All bus modules and documentation: Delete
   All chip modules and documentation: Delete