* doc/bison.texinfo (Mystery Conflicts): Hint '-v' use.

From Golubev I. N.

ChangeLog

@@ -1,3 +1,8 @@
+2001-11-25  Marc Autret  <[email protected]>
+
+	* doc/bison.texinfo (Mystery Conflicts): Hint '-v' use.
+	From Golubev I. N.
+
 2001-11-23  Akim Demaille  <[email protected]>
 
 	* lib/alloca.c: Update, from fileutils.

THANKS

@@ -9,6 +9,7 @@ Daniel Hagerty          [email protected]
 David J. MacKenzie      [email protected]
 Dick Streefland		[email protected]
 Fabrice Bauzac          [email protected]
+Golubev I. N		[email protected]
 Hans Aberg              [email protected]
 Jesse Thilo             [email protected]
 Jim Meyering            [email protected]

doc/bison.texinfo

@@ -4506,8 +4506,9 @@ 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, and adding something to make them
+parser states that are being confused (using @samp{-v}
-look distinct.  In the above example, adding one rule to
+(@pxref{Invocation, ,Invoking Bison}) can help), 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