From: Elena Zannoni <ezannoni@redhat.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: jimb@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: RFA: document binutils support for separate debug info
Date: Thu, 26 Jun 2003 14:08:00 -0000 [thread overview]
Message-ID: <16122.65508.160806.984501@localhost.redhat.com> (raw)
In-Reply-To: <2427-Thu26Jun2003064719+0300-eliz@elta.co.il>
Eli Zaretskii writes:
> > From: Jim Blandy <jimb@redhat.com>
> > Date: 25 Jun 2003 12:35:00 -0500
> >
> > 2003-06-25 Jim Blandy <jimb@redhat.com>
> >
> > * gdb.texinfo (Separate Debug Files): Update documentation to
> > describe GNU Binutils' support for separate debug info files.
>
> Approved. Thanks.
Wait a second. I am fixing gdb bugs ATM with that code.
I think let's hold the doco until it works completely.
elena
next prev parent reply other threads:[~2003-06-26 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 18:31 Jim Blandy
2003-06-26 5:06 ` Eli Zaretskii
2003-06-26 14:08 ` Elena Zannoni [this message]
2003-06-27 6:40 ` Jim Blandy
2003-06-27 12:28 ` Andrew Cagney
2003-06-27 17:30 ` 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=16122.65508.160806.984501@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=eliz@elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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