diff options
| author | Bruce Korb <bkorb@gnu.org> | 2012-10-29 16:44:34 +0000 |
|---|---|---|
| committer | Bruce Korb <bkorb@gnu.org> | 2012-10-29 16:44:34 +0000 |
| commit | 780a250608d6a1cb5c3007a557d213c6cd783c1d (patch) | |
| tree | 041ab47b1a5538f005ec95ec88d8276481253110 /fixincludes/README | |
| parent | eacfc0cb62f7291fce4fe0c3f951513e86e134b0 (diff) | |
Omit testing wrap and replacement fixes during testing.
This exposes a missing result and tests a test that got hidden before.
git-svn-id: https://gcc.gnu.org/svn/gcc/trunk@192952 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'fixincludes/README')
| -rw-r--r-- | fixincludes/README | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/fixincludes/README b/fixincludes/README index c7144a0ba29..9b482102b28 100644 --- a/fixincludes/README +++ b/fixincludes/README @@ -44,6 +44,9 @@ To make your fix, you will need to do several things: Make sure it is now properly handled. Add tests to the "test_text" entry(ies) that validate your fix. This will help ensure that future fixes won't negate your work. + Do *NOT* specify test text for "wrap" or "replacement" fixes. + There is no real possibility that these fixes will fail. + If they do, you will surely know straight away. 5. Go into the fixincludes build directory and type, "make check". You are guaranteed to have issues printed out as a result. |