From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=mnW6=A7=gnu.org=eliz@sourceware.org>
Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10])
	by sourceware.org (Postfix) with ESMTPS id 944A3385783F
	for <gdb-patches@sourceware.org>; Wed, 10 May 2023 18:02:18 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 944A3385783F
Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gnu.org
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gnu.org
Received: from fencepost.gnu.org ([2001:470:142:3::e])
	by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.90_1)
	(envelope-from <eliz@gnu.org>)
	id 1pwo8o-0007rF-7j; Wed, 10 May 2023 14:02:18 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
	s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date:
	mime-version; bh=/+QiEbHB9AiPV6z/edf1YrBchAuTfqwOpyxOvvwDIPM=; b=KfpBDhEGR4Rk
	T+YOzXT4/QJCCEQ3t6KUxjcDGiMtV6e9XP46T//Xy0oTIrkiWQh+bcpVFYBKjgP737aZ6zuMDH9GL
	G3ZCHe9Tu1Z5kXbenB5l+5VATuydH+E749GJ5zNf7OfTcrNU8W+50tD05iiNuiB89nFIyMgowe8Sx
	4SfLlwfSFDnyoj7lE4TIaGRUF26VjNfvrS6G5Mrh4T0LWNtv5d2wYVCwlnF7ik5CIjRpOsGR9mfnI
	i9jZ0XRsN2ZahKDU35VwZcqG4BYWVJFCEHff7GzWErnebr9hgipstlyqHWZsASn52etiNNnmY03d4
	aYuqzFHrCF5Woi31Ois6Zg==;
Received: from [87.69.77.57] (helo=home-c4e4a596f7)
	by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.90_1)
	(envelope-from <eliz@gnu.org>)
	id 1pwo8m-0004my-Ro; Wed, 10 May 2023 14:02:17 -0400
Date: Wed, 10 May 2023 21:03:22 +0300
Message-Id: <83edno6p3p.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
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)
Subject: Re: [PATCH] Add "scheduler-locking" to documentation index
References: <20230510165857.1150392-1-tromey@adacore.com>
X-Spam-Status: No, score=-8.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,GIT_PATCH_0,SPF_HELO_PASS,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org
List-Id: <gdb-patches.sourceware.org>

> 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.