From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23597 invoked by alias); 16 Oct 2013 20:06:27 -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 23580 invoked by uid 89); 16 Oct 2013 20:06:26 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout21.012.net.il Received: from mtaout21.012.net.il (HELO mtaout21.012.net.il) (80.179.55.169) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 16 Oct 2013 20:06:25 +0000 Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0MUS00E002FWZY00@a-mtaout21.012.net.il> for gdb-patches@sourceware.org; Wed, 16 Oct 2013 23:06:22 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MUS00EZB2ILPAA0@a-mtaout21.012.net.il>; Wed, 16 Oct 2013 23:06:22 +0300 (IDT) Date: Wed, 16 Oct 2013 20:06:00 -0000 From: Eli Zaretskii Subject: Re: gdb.texinfo is getting too big In-reply-to: <525EEE89.9060907@redhat.com> To: Pedro Alves Cc: dje@google.com, gdb-patches@sourceware.org, stan@codesourcery.com Reply-to: Eli Zaretskii Message-id: <83txghnfpe.fsf@gnu.org> References: <83ob6rpqa5.fsf@gnu.org> <83mwmbp80v.fsf@gnu.org> <83zjq9nipu.fsf@gnu.org> <525EEE89.9060907@redhat.com> X-IsSubscribed: yes X-SW-Source: 2013-10/txt/msg00497.txt.bz2 > Date: Wed, 16 Oct 2013 20:52:41 +0100 > From: Pedro Alves > CC: Doug Evans , gdb-patches@sourceware.org, > stan@codesourcery.com > > 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. You are talking about splitting the manual, whereas Doug was talking about splitting the sources while keeping a single manual as output. 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.