On Tue, Oct 23, 2012 at 03:59:07PM -0400, Eitan Adler wrote:
> On 23 October 2012 12:54, David Magda wrote:
> > On Tue, October 23, 2012 10:39, Fbsd8 wrote:
> >>
> >> The subject is Google Code-In and all the posted tasks are directed at
> >> creating documentation. Not one deals with coding any p
On Wed, Oct 24, 2012 at 1:11 PM, Lars Engels wrote:
> On Tue, Oct 23, 2012 at 03:59:07PM -0400, Eitan Adler wrote:
>> On 23 October 2012 12:54, David Magda wrote:
>> > On Tue, October 23, 2012 10:39, Fbsd8 wrote:
>> >>
>> >> The subject is Google Code-In and all the posted tasks are directed at
>
On 24 October 2012 13:24, Fernando Apesteguía
wrote:
> Also related to that, what about writing a section about redports[1]
> in the porter's handbook[2]?
This is a good documentation task... but we need more *coding* tasks as well.
> And as a side question, shouldn't some (or all) of these task
(cc'ing -ports and cutting most of the rest)
> From: Eitan Adler
.>
>On 24 October 2012 13:24, Fernando Apesteguía wrote:
>> Also related to that, what about writing a section about redports[1]
>> in the porter's handbook[2]?
>
>This is a good documentation task... but we need more *coding* task
On Wed, Oct 24, 2012 at 7:36 PM, Eitan Adler wrote:
> On 24 October 2012 13:24, Fernando Apesteguía
> wrote:
>> Also related to that, what about writing a section about redports[1]
>> in the porter's handbook[2]?
>
> This is a good documentation task... but we need more *coding* tasks as well.
W
2012/10/25 Pedro Giffuni
> (cc'ing -ports and cutting most of the rest)
>
> > From: Eitan Adler
> .>
> >On 24 October 2012 13:24, Fernando Apesteguía wrote:
> >> Also related to that, what about writing a section about redports[1]
> >> in the porter's handbook[2]?
> >
> >This is a good documentat
6 matches
Mail list logo
