public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jens Axboe <axboe@kernel•dk>
Cc: Tejun Heo <tj@kernel•org>,
	Linux-Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: new maintainer/tree for the libata tree?
Date: Tue, 28 Aug 2018 11:28:51 +1000	[thread overview]
Message-ID: <20180828112851.19c64e80@canb.auug.org.au> (raw)
In-Reply-To: <27ef8afc-c490-5984-5a18-1ee5ce51d556@kernel.dk>

[-- Attachment #1: Type: text/plain, Size: 652 bytes --]

Hi Jens,

On Mon, 27 Aug 2018 19:15:23 -0600 Jens Axboe <axboe@kernel•dk> wrote:
>
> On 8/27/18 3:20 PM, Stephen Rothwell wrote:
> > 
> > I noticed the maintaership change - so what shuld I sues for linux-next,
> > now?
> > 
> > I currently have
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git#for-next  
> 
> I'll merge into my for-next branch on the block tree, I'm don't plan on
> doing separate trees for this, just separate branches. And everything I
> queue up for the next version will end up in my for-next branch.

So I'll just drop the libata tree from linux-next, then?
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-08-28  1:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-27 21:20 linux-next: new maintainer/tree for the libata tree? Stephen Rothwell
2018-08-28  1:15 ` Jens Axboe
2018-08-28  1:28   ` Stephen Rothwell [this message]
2018-08-28  1:30     ` Jens Axboe
2018-08-28  2:43       ` Stephen Rothwell

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=20180828112851.19c64e80@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=axboe@kernel$(echo .)dk \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=tj@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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