From: David Sterba <dsterba@suse.cz>
To: Philippe Loctaux <phil@philippeloctaux.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [Question]: Contributing to btrfs
Date: Mon, 22 Feb 2016 18:15:14 +0100 [thread overview]
Message-ID: <20160222171514.GG4374@suse.cz> (raw)
In-Reply-To: <20160222164054.GB2267@carbon.home>
On Mon, Feb 22, 2016 at 05:41:50PM +0100, Philippe Loctaux wrote:
> On Mon, Feb 22, 2016 at 01:18:05PM +0100, David Sterba wrote:
> >
> > Thanks for the writeup. Should we ever need it again, it's now on the
> > wiki.
> >
> > https://btrfs.wiki.kernel.org/index.php/Developer's_FAQ#How_not_to_start
>
> Thanks for putting that on the wiki, so that the new persons (hopefully)
> won't make the same mistakes that I did :)
>
> Is there a way we can put this onto the main kernel wiki so that almost
> anyone can read that, not just the btrfs people?
I don't think there's one style that fits all subsystems/maintainers and
can be recommended as general practice and I certainly do not want to
maintain any such guide on a wiki. There are guides, posts and
recommendations on how to contribute to linux kernel but they depend on
the acutal maintainers and the preferences. This can change over time.
IMO it's good to lurk for a while and observe the local habits.
next prev parent reply other threads:[~2016-02-22 17:15 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
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 [this message]
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=20160222171514.GG4374@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=phil@philippeloctaux.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.