From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Philippe Loctaux <phil@philippeloctaux.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [Question]: Contributing to btrfs
Date: Mon, 22 Feb 2016 15:34:32 +0800 [thread overview]
Message-ID: <56CABA08.2000403@cn.fujitsu.com> (raw)
In-Reply-To: <20160222072659.GC17243@carbon.ljdarc.local>
Philippe Loctaux wrote on 2016/02/22 08:26 +0100:
> On Mon, Feb 22, 2016 at 09:18:04AM +0800, Qu Wenruo wrote:
>> https://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
>> For branch, normally I use 'integration-X.X' as base for kernel development.
>>
>> And for btrfs-progs,
>> https://github.com/kdave/btrfs-progs.git devel
>
> Allright, I'll work from these repos!
>
> Is it fine if I work from Linus's repo?
> Will my patches get rejected if I do so?
It depends.
If it's just small fix, and can be applied on Chris' integration branch,
that's OK.
In that case, just submit patches to mail list, and if it's OK,
maintainers like David will pick and rebase them properly.
But for huge modifications, it's recommended to use integration branch,
as the final pull request is sent to btrfs maintainer Chris, not Linus.
Although all above is just my personal experience, other developers may
give better advice though.
Thanks,
Qu
>
> --
> Philippe Loctaux
> phil@philippeloctaux.com
>
>
next prev parent reply other threads:[~2016-02-22 7:34 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 [this message]
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
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=56CABA08.2000403@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).