This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Share options between info and man page
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Mingjie Xing <mingjie dot xing at gmail dot com>
- Cc: Eli Zaretskii <eliz at gnu dot org>, Pedro Alves <palves at redhat dot com>, gdb-patches at sourceware dot org
- Date: Mon, 7 Jul 2014 07:18:43 -0700
- Subject: Re: [patch] Share options between info and man page
- Authentication-results: sourceware.org; auth=none
- References: <CADNgcEwweARHgsH5ppJEY=Q8UrtKK7xi8mU6BN7EbjUs=ic1xg at mail dot gmail dot com> <8338fc1wed dot fsf at gnu dot org> <53983FFA dot 6020909 at redhat dot com> <CADNgcEwURN4xMTdMxqhb_poZ=mttgD5FmDNBeezumQgsagaUMw at mail dot gmail dot com> <53A82F8B dot 7080507 at redhat dot com> <CADNgcEz08cCEFTYUNN5gm7AxMGbmmZJMjy2pEYmHbVQO7vHePg at mail dot gmail dot com> <83wqc6qp2r dot fsf at gnu dot org> <CADNgcEwpYHJQSyBtYcwu+P_GuWsNXLhyQiC5b75bZm77ZogOnw at mail dot gmail dot com> <CADNgcEzJeWQh-rt57hVsyZnq7qVfR2dJCV9X5tu4jDyu=mNFyw at mail dot gmail dot com> <CADNgcExxHuj=aapNZAV7EGn7tyms8PnENwu8CS2NC_0nEpx=4A at mail dot gmail dot com>
> Ping.
>
> 2014-06-26 17:34 GMT+08:00 Mingjie Xing <mingjie.xing@gmail.com>:
> > I'd like to put an updated patch for both gdb.texinfo and texi2pod.pl,
> > plus the new comparing result.
> >
> > etc/ChangeLog:
> >
> > * texi2pod.pl (postprocess): Move command process for '@sc' to the
> > front of '@dfn'. Add a new command process for '@t{...}', just print
> > the content.
> >
> > gdb/doc/ChangeLog:
> >
> > * gdb.texinfo (Man Pages): Remove the content of man OPTIONS
> > gdb, add
> > a cross reference to 'Invoking GDB'.
> > (Invoking GDB): Share the option sub-sections with man OPTIONS
> > gdb,
> > move the uniqe part of man here. To display correrctly in man
> > page,
> > change '@xref' after a comma to 'see @ref', and change '@table
> > @code'
> > to '@table @env'.
This is a documentation patch, so best to attract the documentation
maintainer's attention by adding something like "DOCO" in the email
subject.
Also, I think I saw that your patch was missing context info (ie,
straight diff), making it really hard to review. My suggestion is
to work straight off the git repository, to commit the change,
and then to email the patch. "git send-email" is very handy in
that regard.
--
Joel