Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: brobecker@adacore.com, mingjie.xing@gmail.com,
	gdb-patches@sourceware.org
Subject: Re: [patch] Share options between info and man page
Date: Tue, 08 Jul 2014 14:59:00 -0000	[thread overview]
Message-ID: <83k37ndhhq.fsf@gnu.org> (raw)
In-Reply-To: <53BBBE39.6040904@redhat.com>

> Date: Tue, 08 Jul 2014 10:47:37 +0100
> From: Pedro Alves <palves@redhat.com>
> CC: mingjie.xing@gmail.com, gdb-patches@sourceware.org
> 
> >  On top of that, this
> > whole "produce man pages from Texinfo" business was sold to us on the
> > assumption that "it makes maintenance simpler" (see
> > https://sourceware.org/ml/gdb-patches/2013-02/msg00290.html and the
> > discussions around it).  To me this means that we put a bunch of
> > telltale markers into the Texinfo files, add a few Makefile rules, and
> > promptly forget everything we knew about that.
> > 
> > But now it sounds like this arrangement is not simple at all, that we
> > need non-trivial changes to follow (which will probably stump someone
> > at some point, and perhaps even be changed and break the man-page
> > generation), we need to maintain texi2pod.pl, and whatnot else.
> 
> I found some documention on texi2pod.pl here:
> 
>  https://gcc.gnu.org/onlinedocs/gccint/Man-Page-Generation.html
> 
> Sounds like we actually want '@table @gcctabopt'.
> 
> > So I'm beginning to doubt that this is for the better.
> 
> I think the benefits once this is in place outweigh the hurdle we're
> going through.  I'd rather have a synced man page with the occasional
> odd formatting (that gets fixed eventually) than having to keep
> the two texts in sync manually.

In that case, if everyone else is happy with the patch, please approve
it, and let's see what happens next.


      reply	other threads:[~2014-07-08 14:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09  8:40 Mingjie Xing
2014-06-09 14:52 ` Eli Zaretskii
2014-06-10  0:46   ` Mingjie Xing
2014-06-10  2:52     ` Eli Zaretskii
2014-06-10  7:00       ` Mingjie Xing
2014-06-10  7:03         ` Mingjie Xing
2014-06-10 17:56         ` Eli Zaretskii
2014-06-11 11:39           ` Pedro Alves
2014-06-12  3:36             ` Mingjie Xing
2014-06-23 13:45               ` Pedro Alves
2014-06-24  7:08                 ` Mingjie Xing
2014-06-24 15:56                   ` Eli Zaretskii
2014-06-25  1:30                     ` Mingjie Xing
2014-06-26  9:34                       ` Mingjie Xing
2014-07-07  1:12                         ` Mingjie Xing
2014-07-07 14:18                           ` Joel Brobecker
2014-07-07 15:26                             ` Eli Zaretskii
2014-07-07 15:31                               ` Joel Brobecker
2014-07-08  9:47                               ` Pedro Alves
2014-07-08 14:59                                 ` Eli Zaretskii [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83k37ndhhq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mingjie.xing@gmail.com \
    --cc=palves@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox