From: Tom Tromey <tromey@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add "scheduler-locking" to documentation index
Date: Thu, 11 May 2023 09:27:25 -0600 [thread overview]
Message-ID: <87o7mq51nm.fsf@tromey.com> (raw)
In-Reply-To: <83edno6p3p.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 10 May 2023 21:03:22 +0300")
>> +@kindex set scheduler-locking
>> +@cindex scheduler-locking
>> @cindex scheduler locking mode
>> @cindex lock scheduler
>> Set the scheduler locking mode. It applies to normal execution,
Eli> Thanks. I don't object, but do we really need both index entries? I
Eli> think the second one should be enough. But if you insist, I'm okay
Eli> with having both.
I removed the first & I'm checking it in.
Tom
prev parent reply other threads:[~2023-05-11 15:27 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
2023-05-11 15:27 ` Tom Tromey [this message]
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=87o7mq51nm.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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).