From: Jeremy Bennett <jeremy.bennett@embecosm.com>
To: gdb@sourceware.org
Subject: Re: HOWTO for porting GDB published
Date: Tue, 09 Sep 2008 07:01:00 -0000 [thread overview]
Message-ID: <1220943608.2827.44.camel@thomas> (raw)
In-Reply-To: <20080909041745.GM25711@adacore.com>
On Mon, 2008-09-08 at 21:17 -0700, Joel Brobecker wrote:
> I haven't had a chance to look too deeply into it as I am really really
> busy these days, but I think this is a great effort that I'm sure lots
> of people who haven't done a new port before will very much appreciate.
Thank you
> To give your document a little more visibility, I suggest putting
> a link to it on the GDB wiki. Would that make sense to everyone?
I would be very happy with this
Jeremy
--
Tel: +44 (1202) 416955
Cell: +44 (7970) 676050
SkypeID: jeremybennett
Email: jeremy.bennett@embecosm.com
Web: www.embecosm.com
next prev parent reply other threads:[~2008-09-09 7:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 10:53 Jeremy Bennett
2008-09-03 15:38 ` Robert Norton
2008-09-09 4:18 ` Joel Brobecker
2008-09-09 7:01 ` Jeremy Bennett [this message]
2008-09-13 23:09 ` Thiago Jung Bauermann
[not found] ` <1221346443.28258.50.camel@localhost.localdomain>
2008-09-16 9:39 ` Jeremy Bennett
2010-03-23 4:49 ` arm-none-linux-gnuabi - sim support? Reddy, MR Swami
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=1220943608.2827.44.camel@thomas \
--to=jeremy.bennett@embecosm.com \
--cc=gdb@sourceware.org \
/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