From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id HMdANBUbJ2Nl4jsAWB0awg (envelope-from ) for ; Sun, 18 Sep 2022 09:20:21 -0400 Received: by simark.ca (Postfix, from userid 112) id CEAC01E112; Sun, 18 Sep 2022 09:20:21 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=mSqmXXgh; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 7DED81E0D3 for ; Sun, 18 Sep 2022 09:20:21 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 151D33865C26 for ; Sun, 18 Sep 2022 13:20:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 151D33865C26 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1663507221; bh=aq5wBzFjihpND6V5s8E183kpw7Xmfc38C/7UOKQQcgY=; h=Date:To:In-Reply-To:Subject:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=mSqmXXghhDtO6NFK+OEPj+baIqEowwR+nfa2SmejTTBp8B/J7RUPWzrk2ACp/hSCV UMXAwnB3eqZbNZMW7JlvLkeFtCEtTb920RTtbNT7aCFSnIYmhrOfP+OdtfPsMMGp46 z/c8kLrK+/Knzifbv2yp/wscuz7qWsdwrM5oW/3A= Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id 417193858C00 for ; 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 ) 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 ) 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> To: Tom de Vries In-Reply-To: (message from Tom de Vries on Sun, 18 Sep 2022 10:31:43 +0200) Subject: Re: gdb and sphinx documentation References: MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Eli Zaretskii via Gdb-patches Reply-To: Eli Zaretskii Cc: gdb-patches@sourceware.org Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" > Date: Sun, 18 Sep 2022 10:31:43 +0200 > Cc: Eli Zaretskii > From: Tom de Vries > > 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).