public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add "scheduler-locking" to documentation index
Date: Wed, 10 May 2023 21:03:22 +0300	[thread overview]
Message-ID: <83edno6p3p.fsf@gnu.org> (raw)
In-Reply-To: <20230510165857.1150392-1-tromey@adacore.com> (message from Tom Tromey via Gdb-patches on Wed, 10 May 2023 10:58:57 -0600)

> Cc: Tom Tromey <tromey@adacore.com>
> Date: Wed, 10 May 2023 10:58:57 -0600
> From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
> 
> I noticed that "scheduler-locking" does not appear in the index of the
> gdb manual.  This patch corrects this oversight.
> ---
>  gdb/doc/gdb.texinfo | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index 4ae84ec5a63..34552b6b80c 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -7048,6 +7048,8 @@ locking the OS scheduler to allow only a single thread to run.
>  
>  @table @code
>  @item set scheduler-locking @var{mode}
> +@kindex set scheduler-locking
> +@cindex scheduler-locking
>  @cindex scheduler locking mode
>  @cindex lock scheduler
>  Set the scheduler locking mode.  It applies to normal execution,

Thanks.  I don't object, but do we really need both index entries?  I
think the second one should be enough.  But if you insist, I'm okay
with having both.

  reply	other threads:[~2023-05-10 18:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 16:58 Tom Tromey
2023-05-10 18:03 ` Eli Zaretskii [this message]
2023-05-11 15:27   ` Tom Tromey

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=83edno6p3p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@adacore.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).