Re: GSoC Status Report #3

Re: GSoC Status Report #3

[Thiago Jung Bauermann]

Em Sábado 18 Julho 2009 12:12:59 Oguz Kayral escreveu:
> * Event class is almost finished.
> * Started making the necessary changes on InferiorThread class.

Thanks for the report, Oguz. Just to let folks know, we also have private 
conversation on IRC and even once on Skype. Also, Oguz has been discussing his 
work with folks at the #gdb IRC channel.

We're now aiming to move more and more of the GSoC discussions to the GDB 
mailing lists since here's where most of the GDB hackers hang around... Expect 
to see more and more noise (or signal, if you're an optimist!) from us here. 
If any hacker or lurker has suggestions or questions about the GSoC work, feel 
free to join the discussions.

> Plans for next week;
>
> o Put finishing touches on event class.

I saw the code you sent me privately and it indeed looks good (Tromey had 
already said that it seems). It'd be good if you could push the event class 
into the archer-tromey-python branch when you finish working on this bullet. 
What do you think?

> o Further improve InferiorThread class.
> o Start making the necessary changes on Inferior class.

The same goes for the other bullets: it's better to incrementaly push your 
work, and these bullets look like good intermediate steps to do that.
-- 
[]'s
Thiago Jung Bauermann

Re: GSoC Status Report #3

[Tom Tromey]

>>>>> "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.

Oguz, if you want a personal place to commit things, feel free to make
your own branch.  There's some info and rules on doing this on the wiki,
in one of the Archer pages.

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.

Tom

Re: GSoC Status Report #3

[Thiago Jung Bauermann]

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

Re: GSoC Status Report #3

[Oguz Kayral]

I also think creating a new branch is the right way to do this. I'd be
happy to see you guys agree upon a name so that I don't create a
branch that will break conventions.

The main problem with branch creation and pushing is the computer I
used for GSoC has broken last week. I have moved to another computer
and my ssh keypair is gone with the old one. I have created a new one
and I'm mailing it to overseers[at]sourceware.com now. I'll start
pushing as soon as it's replaced.

2009/7/21 Thiago Jung Bauermann <thiago.bauermann@gmail.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

Re: GSoC Status Report #3

[Oguz Kayral]

> I'm mailing it to overseers[at]sourceware.com now. I'll start
> pushing as soon as it's replaced.

This was supposed to be overseers@sourceware.org.

Re: GSoC Status Report #3

[Tom Tromey]

>>>>> "Thiago" == Thiago Jung Bauermann <thiago.bauermann@gmail.com> writes:

Thiago> Just to be clear: the GSoC work is NOT under the Archer
Thiago> umbrella. So it doesn't have to follow the Archer rules. And I
Thiago> strongly prefer that the branch name doesn't start with the
Thiago> archer- prefix.

That is fine by me.  The only reason for the archer- prefix is to avoid
clashes with any branch names from gdb; but probably any name including
"oguz" is also unlikely to cause problems :-)

Tom

Re: GSoC Status Report #3

[Thiago Jung Bauermann]

Em Terça-feira 21 Julho 2009 13:57:51 Tom Tromey escreveu:
> >>>>> "Thiago" == Thiago Jung Bauermann <thiago.bauermann@gmail.com>
> >>>>> writes:
>
> Thiago> Just to be clear: the GSoC work is NOT under the Archer
> Thiago> umbrella. So it doesn't have to follow the Archer rules. And I
> Thiago> strongly prefer that the branch name doesn't start with the
> Thiago> archer- prefix.
>
> That is fine by me.  The only reason for the archer- prefix is to avoid
> clashes with any branch names from gdb; but probably any name including
> "oguz" is also unlikely to cause problems :-)

Awesome. What about "gsoc-oguz-python"? I know, creativity in coming up with 
names is not one of my turn ons...

As for branch rules, since this will be Oguz' playground, I guess the only 
rule is whatever makes him work productively, WDYT? :-)

Oguz, there are some git tips in 
http://sourceware.org/gdb/wiki/ArcherBranchManagement which may help you 
(e.g., merging from master, extracting a patch, etc.).
-- 
[]'s
Thiago Jung Bauermann

Re: GSoC Status Report #3

[Tom Tromey]

>>>>> "Thiago" == Thiago Jung Bauermann <thiago.bauermann@gmail.com> writes:

Thiago> Awesome. What about "gsoc-oguz-python"? I know, creativity in
Thiago> coming up with names is not one of my turn ons...

Thiago> As for branch rules, since this will be Oguz' playground, I
Thiago> guess the only rule is whatever makes him work productively,
Thiago> WDYT? :-)

It all sounds fine to me.

Tom

GSoC Status Report #3

[Oguz Kayral]

Hi,
Some time has passed since the last report, here is what happened so far.

* Event class is almost finished.
* Started making the necessary changes on InferiorThread class.

Plans for next week;

o Put finishing touches on event class.
o Further improve InferiorThread class.
o Start making the necessary changes on Inferior class.

Regards,
Oguz Kayral