From: "Eli Zaretskii" <eliz@elta.co.il>
To: vinschen@redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: HOWTO move a target from old style multiarched to new style multiarched?
Date: Wed, 11 Jun 2003 18:44:00 -0000 [thread overview]
Message-ID: <3791-Wed11Jun2003214316+0300-eliz@elta.co.il> (raw)
In-Reply-To: <20030611120212.GB30116@cygbert.vinschen.de> (message from Corinna Vinschen on Wed, 11 Jun 2003 14:02:12 +0200)
> Date: Wed, 11 Jun 2003 14:02:12 +0200
> From: Corinna Vinschen <vinschen@redhat.com>
>
> there were a lot of changes in the last couple of months to convert gdb
> to a new way of doing things. That's probably good but I don't know how
> many people actually understand the whole process. I must admit, I don't.
>
> I'm under the impression the documentation is missing an important part.
> There's some sort of description spread over the source code now but it
> doesn't give a coherent picture and I also didn't find that in the docs.
>
> Wouldn't it be possible to write a HOWTO for the poor developer soul,
> who's left behind with a target with now using 80% deprecated functions?
Full agreement. I think such documentation should be in
gdbint.texinfo.
next prev parent reply other threads:[~2003-06-11 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 12:02 Corinna Vinschen
2003-06-11 18:44 ` Eli Zaretskii [this message]
2003-06-12 17:00 ` 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=3791-Wed11Jun2003214316+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=vinschen@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).