public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Indu Bhagat <indu.bhagat@oracle.com>
To: binutils@sourceware.org
Cc: weimin.pan@oracle.com, Indu Bhagat <indu.bhagat@oracle.com>
Subject: [PATCH,V2] sframe/doc: remove usage of xrefautomaticsectiontitle
Date: Wed, 23 Nov 2022 16:28:27 -0800	[thread overview]
Message-ID: <20221124002827.1915219-1-indu.bhagat@oracle.com> (raw)
In-Reply-To: <5e519a63-def9-6a9c-85ab-fcd987875545@suse.com>

[Changes in V2]
  - Keep node name and section title in sync when possible.
[End of changes in V2]

xrefautomaticsectiontitle appears to be available from texinfo 5.0 or
greater.  As such, it is not worthwhile to add requirement for a minimum
necessary makeinfo version.  So remove the usage of it.

Also align node name with section title where possible.

ChangeLog:

	* libsframe/doc/sframe-spec.texi: Remove usage of
	xrefautomaticsectiontitle.
---
 libsframe/doc/sframe-spec.texi | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/libsframe/doc/sframe-spec.texi b/libsframe/doc/sframe-spec.texi
index 41f4ba17d83..0559d7c3882 100644
--- a/libsframe/doc/sframe-spec.texi
+++ b/libsframe/doc/sframe-spec.texi
@@ -1,9 +1,6 @@
 \input texinfo       @c                    -*- Texinfo -*-
 @setfilename sframe-spec.info
 @settitle The SFrame Format
-@ifnottex
-@xrefautomaticsectiontitle on
-@end ifnottex
 
 @copying
 Copyright @copyright{} 2021-2022 Free Software Foundation, Inc.
@@ -395,7 +392,7 @@ used for the function.
 
 @cindex The SFrame FDE info word
 @node The SFrame FDE info word
-@subsection The SFrame FDE info word, sfde_func_info
+@subsection The SFrame FDE info word
 
 The info word is a bitfield split into three parts.  From MSB to LSB:
 
@@ -562,7 +559,7 @@ Further FRE types may be added in future.
 
 @cindex The SFrame FRE info word
 @node The SFrame FRE info word
-@subsection The SFrame FRE info word, sfre_info
+@subsection The SFrame FRE info word
 
 The SFrame FRE info word is a bitfield split into four parts.  From MSB to LSB:
 
-- 
2.37.2


  parent reply	other threads:[~2022-11-24  0:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 22:10 [PATCH] " Indu Bhagat
2022-11-23  9:07 ` Jan Beulich
2022-11-23 22:51   ` Indu Bhagat
2022-11-24  0:28   ` Indu Bhagat [this message]
2022-11-24  7:20     ` [PATCH,V2] " Jan Beulich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221124002827.1915219-1-indu.bhagat@oracle.com \
    --to=indu.bhagat@oracle.com \
    --cc=binutils@sourceware.org \
    --cc=weimin.pan@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).