From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18808 invoked by alias); 19 Feb 2013 18:03:23 -0000 Received: (qmail 18771 invoked by uid 22791); 19 Feb 2013 18:03:21 -0000 X-SWARE-Spam-Status: No, hits=-4.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout21.012.net.il (HELO mtaout21.012.net.il) (80.179.55.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 19 Feb 2013 18:03:07 +0000 Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0MIH00300B4CHI00@a-mtaout21.012.net.il> for gdb-patches@sourceware.org; Tue, 19 Feb 2013 20:01:59 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MIH003VFBFAD270@a-mtaout21.012.net.il>; Tue, 19 Feb 2013 20:01:59 +0200 (IST) Date: Tue, 19 Feb 2013 18:03:00 -0000 From: Eli Zaretskii Subject: Re: [patch+doc] New gdbinit.5 man page In-reply-to: <20130219162741.GA4493@host2.jankratochvil.net> To: Jan Kratochvil Cc: tromey@redhat.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <838v6kp4gu.fsf@gnu.org> References: <20130211201401.GA25391@host2.jankratochvil.net> <83621x5x7d.fsf@gnu.org> <20130212162141.GA4287@host2.jankratochvil.net> <87pq05mdqc.fsf@fleche.redhat.com> <83lias3ybi.fsf@gnu.org> <20130219162741.GA4493@host2.jankratochvil.net> X-IsSubscribed: yes 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 X-SW-Source: 2013-02/txt/msg00510.txt.bz2 > Date: Tue, 19 Feb 2013 17:27:41 +0100 > From: Jan Kratochvil > Cc: Tom Tromey , gdb-patches@sourceware.org > > On Wed, 13 Feb 2013 18:42:25 +0100, Eli Zaretskii wrote: > > I just don't see how it will make maintenance simpler. But I'm > > prepared to be convinced ;-) > > On Tue, 12 Feb 2013 17:11:18 +0100, Eli Zaretskii wrote: > > Why is this better than maintaining man pages in their roff format? > > One reason is that mostly any other format is more convenient to write and > maintain than roff. So that means to write man pages either in pod or in > texinfo (or maybe in some other format but not roff). There's a downside as well: you need Perl to be available. > Another reason is that GDB contributors already have to know texinfo for the > GDB manual updates so it means a more difficult learning curve to require > another documentation format (such as pod) knowledge from contributors. > > Is there some reason why not to have all the GDB man pages in texinfo? If doing that helps people contribute and keep the man pages up to date, let's go for it. Thanks.