From: "Eli Zaretskii" <eliz@elta.co.il>
To: ac131313@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa:doco] inline gdbmi.texinfo and annotate.texinfo in gdb.texinfo
Date: Wed, 26 Mar 2003 04:22:00 -0000 [thread overview]
Message-ID: <7458-Wed26Mar2003061550+0200-eliz@elta.co.il> (raw)
In-Reply-To: <3E80CEE7.6090609@redhat.com> (message from Andrew Cagney on Tue, 25 Mar 2003 16:49:27 -0500)
> Date: Tue, 25 Mar 2003 16:49:27 -0500
> From: Andrew Cagney <ac131313@redhat.com>
>
> The attatched merges the gdbmi.texinfo and annotate.texinfo into
> gdb.texinfo.
>
> Seeing as I was doing annotate, I figured I might as well do gdb/mi. It
> only deletes gdbmi.texinfo, as I've plans for annotate.texinfo.
>
> It also does a s/@example/@smallexample/ on those inlined files.
>
> ok?
I don't mind, but what's the reasons for merging gdbmi.texinfo?
next prev parent reply other threads:[~2003-03-26 4:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 21:49 Andrew Cagney
2003-03-26 4:22 ` Eli Zaretskii [this message]
2003-03-26 22:47 ` Andrew Cagney
2003-03-27 3:50 ` Eli Zaretskii
2003-03-27 15:19 ` Andrew Cagney
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=7458-Wed26Mar2003061550+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.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