From a220f55509520a1a647803657537c0933dc31c09 Mon Sep 17 00:00:00 2001 From: Marc Autret Date: Mon, 26 Nov 2001 19:13:40 +0000 Subject: [PATCH] Revert doc patch. --- ChangeLog | 5 ----- THANKS | 1 - doc/bison.texinfo | 5 ++--- 3 files changed, 2 insertions(+), 9 deletions(-) diff --git a/ChangeLog b/ChangeLog index b7c5a449..d227611f 100644 --- a/ChangeLog +++ b/ChangeLog @@ -34,11 +34,6 @@ conflicts as expected. * tests/regression.at (%expect right): Adjust. -2001-11-25 Marc Autret - - * doc/bison.texinfo (Mystery Conflicts): Hint '-v' use. - From Golubev I. N. - 2001-11-23 Akim Demaille * lib/alloca.c: Update, from fileutils. diff --git a/THANKS b/THANKS index abb0d8ab..346d5977 100644 --- a/THANKS +++ b/THANKS @@ -9,7 +9,6 @@ Daniel Hagerty hag@gnu.org David J. MacKenzie djm@gnu.org Dick Streefland dick.streefland@altium.nl Fabrice Bauzac noon@cote-dazur.com -Golubev I. N gin@mo.msk.ru Hans Aberg haberg@matematik.su.se Jesse Thilo jthilo@gnu.org Jim Meyering meyering@gnu.org diff --git a/doc/bison.texinfo b/doc/bison.texinfo index 7b665633..bf0f790b 100644 --- a/doc/bison.texinfo +++ b/doc/bison.texinfo @@ -4507,9 +4507,8 @@ produce parsers that are very large. In practice, Bison is more useful as it is now. When the problem arises, you can often fix it by identifying the two -parser states that are being confused (using @samp{-v} -(@pxref{Invocation, ,Invoking Bison}) can help), and adding something to -make them look distinct. In the above example, adding one rule to +parser states that are being confused, and adding something to make them +look distinct. In the above example, adding one rule to @code{return_spec} as follows makes the problem go away: @example -- 2.45.2