From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32273 invoked by alias); 8 Aug 2013 20:41:29 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 32262 invoked by uid 89); 8 Aug 2013 20:41:28 -0000 X-Spam-SWARE-Status: No, score=-4.5 required=5.0 tests=AWL,BAYES_05,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RDNS_NONE,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.1 Received: from Unknown (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Thu, 08 Aug 2013 20:41:28 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r78KfJQO000954 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 8 Aug 2013 16:41:19 -0400 Received: from barimba (ovpn-113-128.phx2.redhat.com [10.3.113.128]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r78KfIuh025673 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 8 Aug 2013 16:41:18 -0400 From: Tom Tromey To: Stan Shebs Cc: GDB Development Subject: Re: A new strategy for internals documentation References: <5201781A.3000607@earthlink.net> Date: Thu, 08 Aug 2013 20:41:00 -0000 In-Reply-To: <5201781A.3000607@earthlink.net> (Stan Shebs's message of "Tue, 06 Aug 2013 15:26:34 -0700") Message-ID: <877gfv530y.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-08/txt/msg00027.txt.bz2 >>>>> "Stan" == Stan Shebs writes: Stan> Although GDB has had an internals manual for many years, nobody has Stan> been especially happy with it. It is perennially out of date, Stan> sometimes majorly so, and it is quite incomplete. With the passage of Stan> time, the whole idea of an internals manual has come to seem like a Stan> throwback to the old days, when the prospective GDB hacker's Stan> information had to come from either printed books, or tape archives Stan> downloaded from an FTP site. Stan> Various ideas for how to fix have been floating around, generally with Stan> the goal of improving the manual somehow, but nothing has developed Stan> into action. Stan> I propose a two-pronged strategy, first migrating the internals manual Stan> to the wiki, and then introducing Doxygen for source code Stan> documentation. It all sounds good to me. Please get started :-) Tom