From: hugo rivera <uair00@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] outside the gsoc2009
Date: Tue, 21 Apr 2009 10:31:52 +0200 [thread overview]
Message-ID: <138575260904210131t15788dd1scf349f1577e57671@mail.gmail.com> (raw)
In-Reply-To: <138575260904020553u5b447e0bme8d09775a3fec2d8@mail.gmail.com>
Some days ago I expressed my interest in working on the IMFS
implementation on plan 9 and I was waiting to see if someone would
work on it for the gsoc. Apparently no one is going to, so I would
like to work on it. For sure I need someone to guide me all along the
way, is there anyone willing to do so? Any feedback on this subject is
welcome (even negative :-)
Please do not assume that I am going to work as a gsoc student would,
I am planning to progress slowly but steadily.
Saludos
--
Hugo
prev parent reply other threads:[~2009-04-21 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 10:39 hugo rivera
2009-04-02 12:14 ` erik quanstrom
2009-04-02 12:53 ` hugo rivera
2009-04-21 8:31 ` hugo rivera [this message]
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=138575260904210131t15788dd1scf349f1577e57671@mail.gmail.com \
--to=uair00@gmail.com \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).