From: Eric Anopolsky <erpo41@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Hi!
Date: Wed, 20 Aug 2008 02:43:25 -0600 [thread overview]
Message-ID: <1219221805.15514.13.camel@telesto> (raw)
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
Hi,
I'm new here. For the past few months I've been contributing some code
and discussion to the ZFS-fuse project, but Sun's silence on the
licensing issue has left a bad taste in my mouth. I'm ready to switch
over to the light side of the force, but I have a couple of questions.
1. I've seen and modified the ZFS source code. Even if I never look at
it again, could that poison potential contributions to btrfs?
2. What needs doing? Easy stuff first, please. I've never done kernel
coding.
Cheers,
Eric
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-08-20 8:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 8:43 Eric Anopolsky [this message]
2008-08-20 18:25 ` Hi! Chris Mason
2008-08-21 10:47 ` Hi! Miguel Sousa Filipe
2008-08-24 7:02 ` Hi! Steve Long
2008-08-25 21:56 ` Hi! Miguel Sousa Filipe
2008-09-04 19:07 ` Testsuite Steve Long
2008-08-25 9:06 ` Testsuite (was: Re: Hi!) Steve Long
2008-08-25 12:31 ` Chris Mason
2008-08-25 17:15 ` Christoph Hellwig
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=1219221805.15514.13.camel@telesto \
--to=erpo41@gmail.com \
--cc=linux-btrfs@vger.kernel.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