From: Thiago Jung Bauermann <thiago.bauermann@gmail.com>
To: tromey@redhat.com
Cc: Oguz Kayral <oguzkayral@gmail.com>, gdb ml <gdb@sourceware.org>
Subject: Re: GSoC Status Report #3
Date: Tue, 21 Jul 2009 17:35:00 -0000 [thread overview]
Message-ID: <200907211436.51662.thiago.bauermann@gmail.com> (raw)
In-Reply-To: <m3my6yf2ji.fsf@fleche.redhat.com>
Em Terça-feira 21 Julho 2009 13:01:37 Tom Tromey escreveu:
> >>>>> "Thiago" == Thiago Jung Bauermann <thiago.bauermann@gmail.com>
> >>>>> writes:
>
> Oguz> o Put finishing touches on event class.
>
> Thiago> I saw the code you sent me privately and it indeed looks good
> Thiago> (Tromey had already said that it seems). It'd be good if you
> Thiago> could push the event class into the archer-tromey-python branch
> Thiago> when you finish working on this bullet. What do you think?
>
> Just to be clear, patches to this branch require review.
Of course, sorry I forgot.
> Oguz, if you want a personal place to commit things, feel free to make
> your own branch.
If he'd feel more comfortable with that, I wouldn't oppose.
> There's some info and rules on doing this on the wiki,
> in one of the Archer pages.
Just to be clear: the GSoC work is NOT under the Archer umbrella. So it
doesn't have to follow the Archer rules. And I strongly prefer that the branch
name doesn't start with the archer- prefix.
> I encourage you to push your work often. It is the simplest way for
> other people to follow along and see what you are up to.
+1
--
[]'s
Thiago Jung Bauermann
next prev parent reply other threads:[~2009-07-21 17:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <36a35d480907180812j398bb1ax8889ab1eefca9127@mail.gmail.com>
2009-07-21 2:04 ` Thiago Jung Bauermann
2009-07-21 17:04 ` Tom Tromey
2009-07-21 17:35 ` Thiago Jung Bauermann [this message]
2009-07-21 17:54 ` Oguz Kayral
2009-07-21 17:58 ` Oguz Kayral
2009-07-21 18:02 ` Tom Tromey
2009-07-21 18:15 ` Thiago Jung Bauermann
2009-07-21 18:20 ` Tom Tromey
2009-07-18 15:18 Oguz Kayral
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=200907211436.51662.thiago.bauermann@gmail.com \
--to=thiago.bauermann@gmail.com \
--cc=gdb@sourceware.org \
--cc=oguzkayral@gmail.com \
--cc=tromey@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