From: "Andrey Falko" <ma3oxuct@gmail.com>
To: gnap-dev@lists.gentoo.org
Subject: Re: [gnap-dev] I'm Back: GSoC and repos move
Date: Wed, 14 May 2008 05:10:37 -0400 [thread overview]
Message-ID: <350fc7cf0805140210i282f398kc3504b0429f467f6@mail.gmail.com> (raw)
In-Reply-To: <1210754040.19238.2.camel@alice.wonderland>
On Wed, May 14, 2008 at 4:34 AM, JoseAlberto <bass@gentoo.org> wrote:
> Hola :)
>
> I'm back, after a long time out (i was working in a big company project)
> so now is the moment.
>
> The first step is easy, we will move all our code to google code. Any
> objection?
Sounds good to me. It might be a good way to integrate SoC work (by
giving the student access).
>
> what about SoC?
> how is going?
Right now, the student is working on finishing his semester and his
exams. He'll be ready to go June 7th.
Philipp Riegger and I are his mentors.
>
> best regards
>
> --
> gnap-dev@lists.gentoo.org mailing list
>
>
--
gnap-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-05-14 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 8:34 [gnap-dev] I'm Back: GSoC and repos move JoseAlberto
2008-05-14 9:10 ` Andrey Falko [this message]
2008-05-14 9:19 ` Philipp Riegger
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=350fc7cf0805140210i282f398kc3504b0429f467f6@mail.gmail.com \
--to=ma3oxuct@gmail.com \
--cc=gnap-dev@lists.gentoo.org \
/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