linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Sterba <dsterba@suse.cz>
Cc: Chris Mason <clm@fb.com>, <linux-next@vger.kernel.org>,
	<linux-btrfs@vger.kernel.org>
Subject: Re: Add my git tree for linux-next
Date: Wed, 27 Jan 2016 07:37:18 +1100	[thread overview]
Message-ID: <20160127073718.10ef442f@canb.auug.org.au> (raw)
In-Reply-To: <20160126005914.n5zvov6q3v23hvad@floor.thefacebook.com>

Hi David,

On Mon, 25 Jan 2016 19:59:14 -0500 Chris Mason <clm@fb.com> wrote:
>
> On Tue, Jan 26, 2016 at 10:16:16AM +1100, Stephen Rothwell wrote:
> > 
> > On Mon, 25 Jan 2016 19:24:45 +0100 David Sterba <dsterba@suse.cz> wrote:  
> > >
> > > please add my git tree to linux-next branches
> > > 
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
> > > 
> > > It's not populated yet, I'm planning to add namely other developer
> > > patchsets (targeting the next release cycle) as I'm able to review them.
> > > I won't track all pending patchsets nor all single patches that go to
> > > the mailinglist, due to time reasons.  
> > 
> > What subsystem will these patches relate to? (just btrfs)?  Will you be sending pull
> > requests?  To whom? (Chris and Josef)?  If so, how will this be
> > different to the current btrfs tree?  
> 
> Dave is one of the btrfs maintainers, and I frequently pull in his trees
> directly for my pull requests to Linus.  Getting them earlier exposure in
> linux-next will definitely help.
> 
> If we ever share the pull-request duties to Linus, it'll also be important to
> have Dave's trees in there.

Added from today.  I called it btrfs-kdave.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

  reply	other threads:[~2016-01-26 20:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 18:24 Add my git tree for linux-next David Sterba
2016-01-25 23:16 ` Stephen Rothwell
2016-01-26  0:59   ` Chris Mason
2016-01-26 20:37     ` Stephen Rothwell [this message]
2016-01-26 10:26   ` David Sterba
2016-01-26  1:56 ` Stephen Rothwell
2016-01-26  9:57   ` David Sterba

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=20160127073718.10ef442f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=clm@fb.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).