From 06c991dc63cd680a8b986ce4acc22e1f4c021c7c Mon Sep 17 00:00:00 2001 From: korbb Date: Wed, 22 May 2002 02:38:27 +0000 Subject: [PATCH] describe how to fix up the results after adding/changing an inclhack. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@53719 138bc75d-0d04-0410-961f-82ee72b054a4 --- gcc/fixinc/README | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/gcc/fixinc/README b/gcc/fixinc/README index 06fe879245e..ac7b8f11ed0 100644 --- a/gcc/fixinc/README +++ b/gcc/fixinc/README @@ -34,6 +34,17 @@ definitions file, ``inclhack.def''. Please also send relevant information to gcc-bugs@gcc.gnu.org, gcc-patches@gcc.gnu.org and, please, to me: bkorb@gnu.org. +Once you have made your fix, it is necessary to have at least one +test for it. Specify the test with a "test_text" entry. Run +"make check" in the fixinc directory to verify both that your fix +works (by correctly altering your test text) and that your fix +does not suppress the work of other fixes. You should readily +be able to verify this as the "make check" process will print out +context diffs of fixed files. If everything looks fine, you can +either use the diffs for a patch to the baseline files, or simply +copy the result files (in the "tests/res/" subdirectory) into the +baseline directory ("tests/base"). + Here are the rules for making fixes in the inclhack.def file: 0. If you are not the fixincludes maintainer, please send that -- 2.11.0