This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: failure notice
- From: Andrea Francesco Iuorio <andreafrancesco dot iuorio at gmail dot com>
- To: libc-alpha at sourceware dot org
- Date: Sat, 15 Mar 2014 08:34:53 +0100
- Subject: Re: failure notice
- Authentication-results: sourceware.org; auth=none
- References: <CAMaJsKi+0OA7TuFJZ9b=5vd+nYMv6h1D9Qjw4WC6sNkXkn0jaA at mail dot gmail dot com> <53238bff dot 2623440a dot 583c dot 4d12SMTPIN_ADDED_MISSING at mx dot google dot com>
I thought adding a list of functions name directly in the proposal
isn't a good decision for a presentation. For this reason I use words
like "thread management" for referring to the thrd_create/join/ecc.
functions. But you are right, maybe it is better to explain in details
what i mean when i talk about the functionality I'll implement. I can
introduce before my timeline a list of subsets of threads.h and then
referring to them in the timeline for making my proposal more
accurate.
Thanks for everything.
2014-03-15 0:08 GMT+01:00 <MAILER-DAEMON@sourceware.org>:
> Hi. This is the qmail-send program at sourceware.org.
> I'm afraid I wasn't able to deliver your message to the following addresses.
> This is a permanent error; I've given up. Sorry it didn't work out.
>
> <libc-alpha@sourceware.org>:
> Invalid mime type "text/html" detected in message text or
> attachment. Please send plain text messages only.
> See http://sourceware.org/lists.html#sourceware-list-info for more information.
> Contact libc-alpha-owner@sourceware.org if you have questions about this. (#5.7.2)
>
> --- Below this line is a copy of the message.
>
> Return-Path: <andreafrancesco.iuorio@gmail.com>
> Received: (qmail 12878 invoked by uid 89); 14 Mar 2014 23:08:45 -0000
> Authentication-Results: sourceware.org; auth=none
> X-Virus-Checked: by ClamAV 0.98.1 on sourceware.org
> X-Virus-Found: No
> X-Spam-SWARE-Status: No, score=2.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2
> X-Spam-Status: No, score=2.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2
> X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sourceware.org
> X-Spam-Level: **
> X-HELO: mail-ob0-f182.google.com
> Received: from mail-ob0-f182.google.com (HELO mail-ob0-f182.google.com) (209.85.214.182)
> by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Fri, 14 Mar 2014 23:08:44 +0000
> Received: by mail-ob0-f182.google.com with SMTP id uz6so3280181obc.13
> for <libc-alpha@sourceware.org>; Fri, 14 Mar 2014 16:08:42 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=gmail.com; s=20120113;
> h=mime-version:in-reply-to:references:date:message-id:subject:from:to
> :content-type;
> bh=eO1NZBNqpvJg4XzwoMOOQm1QSKeEn/EdedZ4Ab9vneg=;
> b=Ns/bdQ/zrsQ6FLDC60LmOpz7kLcqmdt7ppVlcQw+F+TWRrujuCHgMP6R/O0ZkqZemf
> ySKsHMDZj8KEf1RVnPt+Gi5VAK6oBcPDQjwdshOCokTMkoyyofKbQCwykozWoomuIIZg
> GEIJ5cnzJQbMudY5M8Q5veMHS7f18Ps9yO5uuy9DVqtLtLQmXbWGDWo76SSRMmom5q2s
> jxsLQkJN11FBgQU9ONd7Vpno21E16yQwF/qgDeyb8af9cuUA1S5dGjZ1vfKhctGJRkl8
> kwA5OTU8eMFmup/obXeAWe+JGHEo8IUH1LzaI2b13oy1AIYsXY/Gv5GWMUrudmHKIceo
> cmQg==
> MIME-Version: 1.0
> X-Received: by 10.182.65.199 with SMTP id z7mr9072324obs.7.1394838522216; Fri,
> 14 Mar 2014 16:08:42 -0700 (PDT)
> Received: by 10.60.3.167 with HTTP; Fri, 14 Mar 2014 16:08:42 -0700 (PDT)
> Received: by 10.60.3.167 with HTTP; Fri, 14 Mar 2014 16:08:42 -0700 (PDT)
> In-Reply-To: <532380C0.4020206@redhat.com>
> References: <CAMaJsKjobBfmxjBRB2WP6MMLiAAD=QTV3bhO=hogeZHxmmotPg@mail.gmail.com>
> <Pine.LNX.4.64.1402261759390.11728@digraph.polyomino.org.uk>
> <CAMaJsKg-4WTvX+XPYXMYXHZvRvUotyYeq7O69Xye4WBE7Zw6Wg@mail.gmail.com>
> <530ED801.4000205@redhat.com>
> <CAMaJsKgzSFnT20Bhyn6XyX+Dqk3D3TBqYcJDm8Ym-yDscftr1Q@mail.gmail.com>
> <CAMaJsKh-Psk2-Q=0rsLSnepXUAJxAevHT+4PN8JY9hZ3S4dWmA@mail.gmail.com>
> <CAMaJsKgqpYAiH-fGD4E3toQiNJrCqEGBskGxGwND1uXFRZ6EJQ@mail.gmail.com>
> <CAMaJsKh5MOT-ZSAeXGyd8RJL1ExT6m3EOY+nm6pNkWChYNn=3A@mail.gmail.com>
> <CAMaJsKiDDBFNoByfmZN=Dyr3dWAz+rMF_KzjCBJOYuuDt5AnWA@mail.gmail.com>
> <53228C92.6050603@redhat.com>
> <CAMaJsKhwexZU2EVDAHZmtBeVDJ9468JVN5UJaBmB_axqtNZ7mA@mail.gmail.com>
> <532380C0.4020206@redhat.com>
> Date: Sat, 15 Mar 2014 00:08:42 +0100
> Message-ID: <CAMaJsKi+0OA7TuFJZ9b=5vd+nYMv6h1D9Qjw4WC6sNkXkn0jaA@mail.gmail.com>
> Subject: Re: Gsoc 2014 project proposal
> From: Andrea Francesco Iuorio <andreafrancesco.iuorio@gmail.com>
> To: "Carlos O'Donell" <carlos@redhat.com>, libc-alpha@sourceware.org
> Content-Type: multipart/alternative; boundary=001a11c1fc2ea2c66a04f4992666
>
> --001a11c1fc2ea2c66a04f4992666
> Content-Type: text/plain; charset=ISO-8859-1
>
> I thought adding a list of functions name directly in the proposal isn't a
> good decision for a presentation. For this reason I use words like "thread
> management" for referring to the thrd_create/join/ecc. functions. But you
> are right, maybe it is better to explain in details what i mean when i talk
> about the functionality I'll implement. I can introduce before my timeline
> a list of subsets of threads.h and then referring to them in the timeline
> for making my proposal more accurate.
>
> Thanks for everything.
> On Mar 14, 2014 11:20 PM, "Carlos O'Donell" <carlos@redhat.com> wrote:
>
>> On 03/14/2014 05:21 PM, Andrea Francesco Iuorio wrote:
>> > Done but i think i should give another pass for error checking, Thank
>> > you for all your time and help.
>> >
>> > 2014-03-14 5:58 GMT+01:00 Carlos O'Donell <carlos@redhat.com>:
>> >>
>> >> Overall it looks good.
>> >>
>> >> The English is understandable. It needs a copy-editing pass.
>> >>
>> >> If I could make one suggestion: Please do not use "GlibC" when
>> >> talking about the project, you should always use "GNU C Library"
>> >> since that is the proper name of the project.
>>
>> Your proposal would look even better if you did some background work
>> to look through the ISO C11 thread.h and pick out the list of functions
>> that you need to implement, along with their data structures and
>> include them in your proposal, along with splitting them up into
>> sets that you can implement.
>>
>> It adds detail to your proposal.
>>
>> Cheers,
>> Carlos.
>>
>
> --001a11c1fc2ea2c66a04f4992666
> Content-Type: text/html; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
>
> <p dir=3D"ltr">I thought adding a list of functions name directly in the pr=
> oposal isn't a good decision for a presentation. For this reason I use =
> words like "thread management" for referring to the thrd_create/j=
> oin/ecc. functions. But you are right, maybe it is better to explain in det=
> ails what i mean when i talk about the functionality I'll implement. I =
> can introduce before my timeline a list of subsets of threads.h and then re=
> ferring to them in the timeline for making my proposal more accurate.</p>
>
> <p dir=3D"ltr">Thanks for everything.</p>
> <div class=3D"gmail_quote">On Mar 14, 2014 11:20 PM, "Carlos O'Don=
> ell" <<a href=3D"mailto:carlos@redhat.com";>carlos@redhat.com</a>>=
> ; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D=
> "margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> On 03/14/2014 05:21 PM, Andrea Francesco Iuorio wrote:<br>
> > Done but i think i should give another pass for error checking, Thank<=
> br>
> > you for all your time and help.<br>
> ><br>
> > 2014-03-14 5:58 GMT+01:00 Carlos O'Donell <<a href=3D"mailto:ca=
> rlos@redhat.com">carlos@redhat.com</a>>:<br>
> >><br>
> >> Overall it looks good.<br>
> >><br>
> >> The English is understandable. It needs a copy-editing pass.<br>
> >><br>
> >> If I could make one suggestion: Please do not use "GlibC"=
> ; when<br>
> >> talking about the project, you should always use "GNU C Libra=
> ry"<br>
> >> since that is the proper name of the project.<br>
> <br>
> Your proposal would look even better if you did some background work<br>
> to look through the ISO C11 thread.h and pick out the list of functions<br>
> that you need to implement, along with their data structures and<br>
> include them in your proposal, along with splitting them up into<br>
> sets that you can implement.<br>
> <br>
> It adds detail to your proposal.<br>
> <br>
> Cheers,<br>
> Carlos.<br>
> </blockquote></div>
>
> --001a11c1fc2ea2c66a04f4992666--
--
Andrea Francesco Iuorio
Student in Computer Science, Università degli Studi di Milano
andreafrancesco.iuorio@gmail.com - GPG Key