From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eric Anopolsky <erpo41@gmail.com>
Subject: Hi!
Date: Wed, 20 Aug 2008 02:43:25 -0600
Message-ID: <1219221805.15514.13.camel@telesto>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-77uYnbqhcvsOo/hZR7ym"
To: linux-btrfs@vger.kernel.org
Return-path: <linux-btrfs-owner@vger.kernel.org>
List-ID: <linux-btrfs.vger.kernel.org>


--=-77uYnbqhcvsOo/hZR7ym
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

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


--=-77uYnbqhcvsOo/hZR7ym
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBIq9kte2L37HVup3ARAntiAKDdJonx9lGce54ZXCMYdvAYV3Wo4QCg3nsh
kCMqhKWfNb3Ovf9BI56j60w=
=CkBF
-----END PGP SIGNATURE-----

--=-77uYnbqhcvsOo/hZR7ym--