On Fri, 8 Nov 2013, H.J. Lu wrote:
> bugreport.texi has
>
> @menu
> * Criteria: Bug Criteria. Have you really found a bug?
> * Reporting: Bug Reporting. How to report a bug effectively.
> * Known: Trouble. Known problems.
> * Help: Service. Where to ask for help.
> @end menu
>
> That means include order should be bugreport.texi, trouble.texi,
> service.texi. And we need to specify next, previous and up nodes to
> Service and Trouble nodes. OK to install?
Thanks for looking into this, H.J.! Looking at the logic we have
been using elsewhere, I am wondering whether it shouldn't be the
order in bugreport.texi that should be adjusted -- switching the
"Known: Trouble" and "Reporting: Bug Reporting" nodes?
That way you could omit
> 2013-11-08 H.J. Lu <hongjiu...@intel.com>
>
> PR other/59055
> * doc/gcc.texi: Move Trouble after Bugs in menu. Include
> trouble.texi after bugreport.texi.
those two changes, and only update bugreport.texi? If this sounds
acceptable, please go ahead and make this change.
> * doc/service.texi: Add next, previous and up nodes to Service
> nodes.
> * doc/trouble.texi: Add next, previous and up nodes to Trouble
> nodes.
Why are these necessary? The texinfo documentation say the following
about @node:
The subsequent arguments are optional—they are the names of the
‘Next’, ‘Previous’, and ‘Up’ pointers, in that order. We strongly
recommend omitting them if your Texinfo document is hierarchically
organized, as virtually all are
Gerald
