From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28392 invoked by alias); 16 Oct 2013 20:10:56 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 28382 invoked by uid 89); 16 Oct 2013 20:10:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: ausc60ps301.us.dell.com Received: from ausc60ps301.us.dell.com (HELO ausc60ps301.us.dell.com) (143.166.148.206) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (CAMELLIA256-SHA encrypted) ESMTPS; Wed, 16 Oct 2013 20:10:55 +0000 X-LoopCount0: from 10.175.216.251 From: To: CC: , , , Subject: Re: gdb.texinfo is getting too big Date: Wed, 16 Oct 2013 20:10:00 -0000 Message-ID: References: <83ob6rpqa5.fsf@gnu.org> <83mwmbp80v.fsf@gnu.org> <83zjq9nipu.fsf@gnu.org> <525EEE89.9060907@redhat.com> <83txghnfpe.fsf@gnu.org> In-Reply-To: <83txghnfpe.fsf@gnu.org> Content-Type: text/plain; charset="us-ascii" Content-ID: <2F974D9C65F3984BA9922347A73A3D89@dell.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes X-SW-Source: 2013-10/txt/msg00500.txt.bz2 On Oct 16, 2013, at 4:06 PM, Eli Zaretskii wrote: >> Date: Wed, 16 Oct 2013 20:52:41 +0100 >> From: Pedro Alves >> CC: Doug Evans , gdb-patches@sourceware.org, >> stan@codesourcery.com >>=20 >> Maybe it'd be easier to think in terms of things that would make >> sense to split out of the main file. E.g., the RSP chapter is useful >> for GDB and stub developers, but not for regular users -- split that >> one out. Python scripting API stuff is useful for advanced users >> that want to extend GDB, but it's not really the same class of manual >> as the other chapters, so split that one out as another file too. >> MI is useful for frontend writers, not for regular users, so out it >> goes too. Whatever other identifiable logic units we find, split >> them out. Then I suspect we'll end up with the core manual for >> regular users that describes GDB's main features/CLI/commands, >> and it'll be lean enough to be manageable. >=20 > You are talking about splitting the manual, whereas Doug was talking > about splitting the sources while keeping a single manual as output. >=20 > I'm not sure I see a good reason to split the manual. For starters, > the size of that doesn't hurt as much as the size of the source file > when you need to edit it. Agreed. There are plenty of examples of large manuals (GCC, GCCint, Emacs)= . Divide them into as many source files as is convenient, that doesn't bot= her any user. But having the manual (what users read) split into multiple = parts is not a good change. If we ever hit 5000 pages I might change my tune, but no GDB documentation = is even close to that big. paul