From: Jie Zhang <jie.zhang@analog.com>
To: Sean Chen <sean.chen1234@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Ramp up documents
Date: Mon, 02 Nov 2009 08:46:00 -0000 [thread overview]
Message-ID: <4AEE9C4C.9070109@analog.com> (raw)
In-Reply-To: <5e81cb500911020012s23a83503vc3c1ae85630fccae@mail.gmail.com>
Sean Chen wrote:
> Hi Jie,
>
> Thanks. ItÂ’s helpful.
>
> Do we have more detailed information? For example, reversible
> debugging TODO list shows that MIPS and ARM port is ongoing, but it
> doesnÂ’t contain the information on the developers and status. Could
> you throw me a hint on how to get this kind of information? Thanks.
>
For ongoing details, this mailing list and gdb-patches mailing list are
great resources. You can search for the latest discussions and patches
on the projects you are interested. If you cannot find the information
you want, you can always ask on this mailing list. The developers who
work on the projects will answer you. I'm not familiar with the projects
you mentioned. So I cannot help here. Sorry.
Jie
next prev parent reply other threads:[~2009-11-02 8:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 5:04 Sean Chen
2009-11-02 6:03 ` Jie Zhang
2009-11-02 8:12 ` Sean Chen
2009-11-02 8:46 ` Jie Zhang [this message]
2009-11-02 9:03 ` Sean Chen
2009-11-03 6:30 ` Hui Zhu
2009-11-03 9:08 ` Sean Chen
2009-11-02 15:17 ` Tom Tromey
2009-11-03 9:12 ` Sean Chen
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=4AEE9C4C.9070109@analog.com \
--to=jie.zhang@analog.com \
--cc=gdb@sourceware.org \
--cc=sean.chen1234@gmail.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