Windows: Use %p for ptrs in redirector trace messages

[openafs.git] / README.WARNINGS

diff --git a/README.WARNINGS b/README.WARNINGS
index 9de861d..4122d33 100644 (file)
--- a/README.WARNINGS
+++ b/README.WARNINGS
@@ -6,7 +6,7 @@ to reduce the number of warnings in the OpenAFS tree. In an attempt to
 prevent warnings from creeping back in, we now have the ability to break the
 build when new warnings appear.
 
-This is only available for systems with gcc 4.2 or later, and is disabled 
+This is only available for systems with gcc 4.2 or later, and is disabled
 unless the --enable-checking option is supplied to configure. Because we
 can't remove all of the warnings, we permit file by file (and warning by
 warning) disabling of specific warnings. The --enable-checking=all prevents
@@ -21,15 +21,15 @@ disabled in an number of ways.
 You can disable a single warning type in a particular file by using GCC
 pragmas. If a warning can be disabled with a pragma, then the switch to use
 will be listed in the error message you receive from the compiler. Pragmas
-should be wrapped in IGNORE_SOME_GCC_WARNINGS, so that they aren't used 
+should be wrapped in IGNORE_SOME_GCC_WARNINGS, so that they aren't used
 with non-gcc compilers, and can be disabled if desired. For example:
   #ifdef IGNORE_SOME_GCC_WARNINGS
   # pragma GCC diagnostic warning "-Wold-style-definition"
   #endif
 
-If a pragma isn't available for your particular warning, you will need to 
+If a pragma isn't available for your particular warning, you will need to
 disable all warnings for the file in question. You can do this by supplying
-the autoconf macro @CFLAGS_NOERROR@ in the build options for the file. For 
+the autoconf macro @CFLAGS_NOERROR@ in the build options for the file. For
 example:
   lex.yy.o : lex.yy.c y.tab.c
          ${CC} -c ${CFLAGS} @CFLAGS_NOERROR@ lex.yy.c