public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Eric Anopolsky <erpo41@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Hi!
Date: Wed, 20 Aug 2008 14:25:50 -0400	[thread overview]
Message-ID: <1219256750.7854.7.camel@think.oraclecorp.com> (raw)
In-Reply-To: <1219221805.15514.13.camel@telesto>

On Wed, 2008-08-20 at 02:43 -0600, Eric Anopolsky wrote:
> 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?
> 

For now, yes, reading and changing the ZFS source code is not a good
idea for people that want to contribute to btrfs.

> 2. What needs doing? Easy stuff first, please. I've never done kernel
> coding.

Testing, discussing and reporting bugs are a great first step.

-chris



  reply	other threads:[~2008-08-20 18:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20  8:43 Hi! Eric Anopolsky
2008-08-20 18:25 ` Chris Mason [this message]
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=1219256750.7854.7.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=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