Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: nickrob@snap.net.nz (Nick Roberts)
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb ml <gdb@sourceware.org>
Subject: GDB and the Google Summer of Code
Date: Tue, 21 Apr 2009 11:36:00 -0000	[thread overview]
Message-ID: <18925.33674.230789.972718@totara.tehura.co.nz> (raw)
In-Reply-To: <1240266843.17964.16.camel@localhost.localdomain>

Thiago Jung Bauermann writes:
 > Hi,
 > 
 > I'm happy to tell you that Oguz Kayral's GSoC proposal has been accepted
 > under the GNU organization! He'll work on adding support for inferior
 > events to the Python API, in particular for inferior signals. I'll be
 > his mentor.

That's good news.

 > You can see the GNU Project's accepted proposals here:
 > 
 > http://socghop.appspot.com/org/home/google/gsoc2009/karlberry
 >
 > And Oguz' proposal here:
 > 
 > http://socghop.appspot.com/student_project/show/google/gsoc2009/karlberry/t124022551612

I'd like to also point to another project, also on the above URL, that I
I will be mentoring:

    Dmitry Dzhus:  Emacs GDB/MI migration

Although Tom Tromey was adamant on the GNU summer-of-code mailing list that
this was not a GDB project, I hope it can enjoy similar support from this
mailing list.  Also that any patches for GDB that we may have could be reviewed
and (possibly) approved within the timescale of the project (about eight
weeks).

TIA

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  parent reply	other threads:[~2009-04-21  8:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 22:40 Thiago Jung Bauermann
2009-04-21  8:28 ` Sérgio Durigan Júnior
2009-04-21 11:36 ` Nick Roberts [this message]
2009-04-21 16:26   ` Tom Tromey
2009-04-22  7:05     ` Nick Roberts
2009-04-22 17:21 ` Hui Zhu

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=18925.33674.230789.972718@totara.tehura.co.nz \
    --to=nickrob@snap.net.nz \
    --cc=bauerman@br.ibm.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