From: Joel Brobecker <brobecker@adacore.com>
To: Mingjie Xing <mingjie.xing@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Pedro Alves <palves@redhat.com>,
gdb-patches@sourceware.org
Subject: Re: [patch] Share options between info and man page
Date: Mon, 07 Jul 2014 14:18:00 -0000 [thread overview]
Message-ID: <20140707141843.GA6038@adacore.com> (raw)
In-Reply-To: <CADNgcExxHuj=aapNZAV7EGn7tyms8PnENwu8CS2NC_0nEpx=4A@mail.gmail.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
next prev parent reply other threads:[~2014-07-07 14:18 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 [this message]
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
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=20140707141843.GA6038@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--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