Re: GSoC Status Report #3

[Oguz Kayral <oguzkayral@gmail.com>]

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