Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [GSoC 2019] Introduction Email - Atharva Lele
Date: Thu, 2 May 2019 21:57:13 +0200	[thread overview]
Message-ID: <20190502195713.GA17072@scaer> (raw)
In-Reply-To: <CABM+sgo1dxV-SzpMn0VS-R0zJm5A2cj2ycH8fOSOLEOCd7FFtw@mail.gmail.com>

Atharva, All,

On 2019-05-03 00:57 +0530, Atharva Lele spake thusly:
> Yann, Arnout, and everyone:
> Just sending a follow-up email since I didn't hear back from you guys. Unfortunately due to
> college assignments I was completely swamped and didn't get a chance to work on GSoC
> as I'd mentioned in my timeline. I can devote a bit more time in this month, so I can catch up
> on my research about Reproducible Builds that I was going to do.?
> If there's anything you want me to know then I'm looking forward to hearing from you.

As described in the official GSoC timeline, the selection step is still
an on-going process, and the final results will be announced on May the
6th:

    https://summerofcode.withgoogle.com/how-it-works/#timeline

Regards,
Yann E. MORIN.

> Regards,
> Atharva Lele
> On Wed, Apr 10, 2019 at 12:08 AM Atharva Lele < [1]itsatharva@gmail.com> wrote:
> 
>   Hello Arnout, Yann, and everyone:
>   I've submitted my final GSoC proposal PDF on the GSoC website.
>   If needed we can share the plan with the mailing list, let me know if that needs
>   to be done.
>   Regards,
>   Atharva Lele
>   On Thu, Apr 4, 2019 at 9:25 PM Atharva Lele < [2]itsatharva@gmail.com> wrote:
> 
>     > I'll do my part of the review later tonight.
>     I have modified and added some parts (in blue color) and highlighted which parts
>     to remove (in red color). Also replied to your comments.
>     If you have any more suggestions please let me know. Meanwhile I will keep looking
>     for more information to improve the technicalities of my draft.
>     Regards,
>     Atharva Lele
>     On Tue, Apr 2, 2019 at 11:49 PM Yann E. MORIN < [3]yann.morin.1998@free.fr> wrote:
> 
>       Atharva, Arnout, All,
> 
>       On 2019-04-02 21:00 +0530, Atharva Lele spake thusly:
>       > > I've made comments on the document.
>       > I've replied to your comments on there. We can discuss a bit more and I think then I'll
>       > make necessary changes to the document.
>       > > I'm not sure if Yann is OK with using
>       > > Googly stuff though.
>       > Is there any other platform that he would be comfortable working on?
>       > I'll gladly move things over to there.
> 
>       Nope, that's fine. It's part of the GSoC ecosystem, so I'll play by the
>       GSoC rules. ;-) I'll do my part of the review later tonight.
> 
>       Regards,
>       Yann E. MORIN.
> 
>       --
>       .-----------------.--------------------.------------------.--------------------.
>       |? Yann E. MORIN? | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
>       | +33 662 376 056 | Software? Designer | \ / CAMPAIGN? ? ?|? ___? ? ? ? ?
>       ? ? ?|
>       | +33 561 099 427 `------------.-------:? X? AGAINST? ? ? |? \e/? There is no? |
>       | [4]http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL? ? |? ?v? ?conspiracy.? |
>       '------------------------------^-------^------------------^--------------------'
> 
> Links:
> 1. mailto:itsatharva at gmail.com
> 2. mailto:itsatharva at gmail.com
> 3. mailto:yann.morin.1998 at free.fr
> 4. http://ymorin.is-a-geek.org/

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2019-05-02 19:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-17 13:46 [Buildroot] [GSoC 2019] Introduction Email - Atharva Lele Atharva Lele
2019-03-26 22:09 ` Arnout Vandecappelle
     [not found]   ` <d528d059-b900-7b18-7772-dbb3350f1af6@mind.be>
     [not found]     ` <CABM+sgpVOb0gxPeA3fTm4Luup6wDgyE56DPB1taVouCB4JmryA@mail.gmail.com>
2019-04-01 16:58       ` Atharva Lele
2019-04-02  9:21         ` Arnout Vandecappelle
2019-04-02 15:30           ` Atharva Lele
2019-04-02 18:19             ` Yann E. MORIN
2019-04-04 15:55               ` Atharva Lele
2019-04-09 18:38                 ` Atharva Lele
2019-05-02 19:27                   ` Atharva Lele
2019-05-02 19:57                     ` Yann E. MORIN [this message]
2019-05-07 13:26                       ` Atharva Lele
2019-05-07 21:17                         ` Yann E. MORIN
2019-05-07 22:12                           ` Arnout Vandecappelle
2019-05-08 11:34                             ` Atharva Lele
2019-05-08 12:21                               ` Yann E. MORIN
2019-05-08 12:51                                 ` Atharva Lele
2019-05-08 13:44                                   ` Arnout Vandecappelle
2019-05-08 13:55                                     ` Atharva Lele
2019-05-08 21:28                               ` Arnout Vandecappelle
2019-05-09  6:49                                 ` Atharva Lele

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=20190502195713.GA17072@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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