From: Simon Quigley <tsimonq2@ubuntu.com>
To: fdmanana@gmail.com, Philippe Loctaux <phil@philippeloctaux.com>
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [Question]: Contributing to btrfs
Date: Mon, 22 Feb 2016 06:02:01 -0600 [thread overview]
Message-ID: <1456142520.3587.3.camel@ubuntu.com> (raw)
In-Reply-To: <CAL3q7H7Ty4R8dQO=MWayn3xzROjRub7uzuGVdM7zMCfU0As1Eg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 424 bytes --]
> 1) You don't learn anything by doing them. You don't learn nothing
> about btrfs internals, filesystems in general, kernel programming in
> general, general programming in C, etc. It ends up being only a waste
> of time for you;
It is useful for one reason. If you would like to get used to the workflow of kernel development,
this seems to be useful for a lot of people. In fact, Linus himself has encouraged this.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-22 12:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 21:09 [Question]: Contributing to btrfs Philippe Loctaux
2016-02-20 22:40 ` Philippe Loctaux
2016-02-21 6:14 ` Duncan
2016-02-22 1:18 ` Qu Wenruo
2016-02-22 7:26 ` Philippe Loctaux
2016-02-22 7:34 ` Qu Wenruo
2016-02-22 7:42 ` Philippe Loctaux
2016-02-22 10:47 ` Filipe Manana
2016-02-22 12:02 ` Simon Quigley [this message]
2016-02-22 13:29 ` Filipe Manana
2016-02-22 14:45 ` Simon Quigley
2016-02-23 1:32 ` Qu Wenruo
2016-02-23 2:07 ` Simon Quigley
2016-02-23 2:20 ` Qu Wenruo
2016-02-22 16:45 ` Philippe Loctaux
2016-02-22 12:18 ` David Sterba
2016-02-22 16:41 ` Philippe Loctaux
2016-02-22 17:15 ` David Sterba
2016-02-22 11:34 ` David Sterba
2016-02-22 16:38 ` Philippe Loctaux
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=1456142520.3587.3.camel@ubuntu.com \
--to=tsimonq2@ubuntu.com \
--cc=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=phil@philippeloctaux.com \
--cc=quwenruo@cn.fujitsu.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.