From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eliz@gnu.org>
Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10])
 by sourceware.org (Postfix) with ESMTPS id 417193858C00
 for <gdb-patches@sourceware.org>; Sun, 18 Sep 2022 13:20:02 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 417193858C00
Received: from fencepost.gnu.org ([2001:470:142:3::e]:44004)
 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 1oZuDJ-0007sj-NM; Sun, 18 Sep 2022 09:20:01 -0400
Received: from [87.69.77.57] (port=3726 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 1oZuDJ-0000Ro-54; Sun, 18 Sep 2022 09:20:01 -0400
Date: Sun, 18 Sep 2022 16:20:02 +0300
Message-Id: <837d20zunx.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
In-Reply-To: <c37bd31e-1c40-8c2e-cc35-5e9f31930bc4@suse.de> (message from Tom
 de Vries on Sun, 18 Sep 2022 10:31:43 +0200)
Subject: Re: gdb and sphinx documentation
References: <c37bd31e-1c40-8c2e-cc35-5e9f31930bc4@suse.de>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Spam-Status: No, score=2.1 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH,
 DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_EU, KAM_SHORT,
 RCVD_IN_BARRACUDACENTRAL, SPF_HELO_PASS, SPF_PASS,
 TXREP autolearn=no autolearn_force=no version=3.4.6
X-Spam-Level: **
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: gdb-patches@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-patches mailing list <gdb-patches.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-patches>,
 <mailto:gdb-patches-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-patches>,
 <mailto:gdb-patches-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Sep 2022 13:20:03 -0000

> Date: Sun, 18 Sep 2022 10:31:43 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>
> From: Tom de Vries <tdevries@suse.de>
> 
> Hi,
> 
> at the GNU Cauldron, Martin Liška presented a BOF about migrating GCC 
> documentation to sphinx format ( 
> https://gcc.gnu.org/wiki/cauldron2022#cauldron2022talks.the_sphinx_documentation_bof 
> ).
> 
> I asked him about the gdb documentation, and he ran the migration 
> scripts he used for gcc on it.  The result is obviously a bit rough, but 
> gives a nice idea what it could look like.
> 
> Please take a look if you're interested ( https://splichal.eu/tmp/gdb ).

I also suggest to become familiar with the long discussion of this on
the GCC list:

  https://gcc.gnu.org/pipermail/gcc/2021-June/236172.html
  https://gcc.gnu.org/pipermail/gcc/2021-June/236604.html
  https://gcc.gnu.org/pipermail/gcc/2021-July/236638.html
  https://gcc.gnu.org/pipermail/gcc/2021-July/236731.html

and with the POV of the Texinfo maintainer:

  https://gcc.gnu.org/pipermail/gcc/2021-July/236756.html

>From my side, I can just say that if GDB decides to migrate to Sphinx,
I will step down as the person responsible for the GDB documentation,
because it's too late for me to learn yet another incompatible
documentation system (and insufficiently documented on top of that).