From: David Sterba <dsterba@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: clm@fb.com, linux-next@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: Add my git tree for linux-next
Date: Tue, 26 Jan 2016 11:26:17 +0100 [thread overview]
Message-ID: <20160126102617.GC8567@suse.cz> (raw)
In-Reply-To: <20160126101616.682677d4@canb.auug.org.au>
On Tue, Jan 26, 2016 at 10:16:16AM +1100, Stephen Rothwell wrote:
> Hi David,
>
> 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?
Just btrfs, pull requests to Chris. As he wrote, this already happens.
Another point is to make it a bit more clear to the other developers
which patchsets/branches are heading upstream. Sorry for lack of details
in the request.
next prev parent reply other threads:[~2016-01-26 10:26 UTC|newest]
Thread overview: 9+ 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 0:59 ` Chris Mason
2016-01-26 20:37 ` Stephen Rothwell
2016-01-26 20:37 ` Stephen Rothwell
2016-01-26 10:26 ` David Sterba [this message]
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=20160126102617.GC8567@suse.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.