From: Tom Tromey <tromey@redhat.com>
To: Sean Chen <sean.chen1234@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Ramp up documents
Date: Mon, 02 Nov 2009 15:17:00 -0000 [thread overview]
Message-ID: <m3r5shhs7y.fsf@fleche.redhat.com> (raw)
In-Reply-To: <5e81cb500911012104h1b7958d8w1041e0c68f249b81@mail.gmail.com> (Sean Chen's message of "Mon, 2 Nov 2009 13:04:36 +0800")
>>>>> "Sean" == Sean Chen <sean.chen1234@gmail.com> writes:
Sean> Do we have some ramp up documents on how to participate in the
Sean> development of GDB besides “GDB Internals”? Do we have the list
Sean> for the ongoing subtasks as well as developers who are working on
Sean> them? I appreciate your help if you can throw me a hint.
In addition to the project ideas on the wiki, another way to get started
is to fix a bug. There are plenty to be found in bugzilla.
Tom
next prev parent reply other threads:[~2009-11-02 15:17 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
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 [this message]
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=m3r5shhs7y.fsf@fleche.redhat.com \
--to=tromey@redhat.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