Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [patch] gdb_gcore man/help/install [+doc] #2
Date: Tue, 20 Dec 2011 14:42:00 -0000	[thread overview]
Message-ID: <m3obv3mhp8.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20111206002555.GA12329@host2.jankratochvil.net> (Jan	Kratochvil's message of "Tue, 6 Dec 2011 01:25:55 +0100")

>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Jan> From the practical point of view with the goal to generate only the
Jan> nroff .1 format I think the choice is clear from nroff, pod and
Jan> texinfo.  The most simple format for maintenance is pod.  Therefore
Jan> I did not use texi2pod at all.

Thanks.  I think it seems fine.

We still need an info node for invoking gcore.

Jan> Another approach would be some reorganization of gdb.texinfo to
Jan> generate also some huge man page from it but I do not plan to do so
Jan> myself.

I looked a little at using texi2pod but it seemed a bit daunting, as the
organization is pretty different.  (The man page wouldn't have to be
enormous, but it does require extra markup and I think the ordering
might have to change.)

Tom


  reply	other threads:[~2011-12-20 14:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-25  7:42 [patch] gdb_gcore man/help/install [+doc] Jan Kratochvil
2011-04-25  8:37 ` Andreas Schwab
2011-04-25  8:43   ` Jan Kratochvil
2011-04-25 15:36 ` Tom Tromey
2011-04-26 20:00   ` Tom Tromey
2011-12-06  0:54   ` [patch] gdb_gcore man/help/install [+doc] #2 Jan Kratochvil
2011-12-20 14:42     ` Tom Tromey [this message]
2011-12-21 21:20       ` Jan Kratochvil

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=m3obv3mhp8.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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