Use minor()/major() instead of "& 0xff" in order to be 32 bit compliant

[dump.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index b382d7f25853cf9831e7392a3a780894837aea57..e90eb975ad32c0fa1fbe89bfce69c3accb5a84f4 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,4 +1,4 @@
-$Id: CHANGES,v 1.239 2004/01/27 10:37:25 stelian Exp $
+$Id: CHANGES,v 1.240 2004/01/28 10:02:31 stelian Exp $
 
 Changes between versions 0.4b35 and 0.4b36 (released ?????????????????)
 =======================================================================
@@ -18,6 +18,12 @@ Changes between versions 0.4b35 and 0.4b36 (released ?????????????????)
        sizes in a single run (make -B accept a list of values).
        Patch contributed by Florian Zumbiehl <florz@gmx.de>.
 
+5.     Use the glibc provided minor() and major() macros instead
+       of our own bitmask implementation. This should be safe for
+       when the major/minor namespace will migrate to 32 bits.
+       Thanks to Zhang Jun <zhangjun@nanjing-fnst.com> for reporting
+       the bug.
+
 Changes between versions 0.4b34 and 0.4b35 (released December 21, 2003)
 =======================================================================