public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Paul Gortmaker <paul.gortmaker@windriver•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: [linux-next] please include init-v4.1-rc6 branch for v4.2
Date: Thu, 16 Jul 2015 10:06:19 +1000	[thread overview]
Message-ID: <20150716100619.33a65928@canb.auug.org.au> (raw)
In-Reply-To: <20150715205903.GB26147@windriver.com>

Hi Paul,

On Wed, 15 Jul 2015 16:59:03 -0400 Paul Gortmaker <paul.gortmaker@windriver•com> wrote:
>
> [Re: [linux-next] please include init-v4.1-rc6 branch for v4.2] On 03/06/2015 (Wed 13:39) Stephen Rothwell wrote:
> 
> > Hi Paul,
> > 
> > On Tue, 2 Jun 2015 19:23:18 -0400 Paul Gortmaker <paul.gortmaker@windriver•com> wrote:
> > >
> > > Please include init-v4.1-rc6 branch of:
> > > 	git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux.git
> > 
> > OK, I will add it in just before I merge Andrew's tree and see how it
> > goes.
> > 
> 
> [...]
> 
> > 
> > > Assuming I can get Linus to pull the chunks this time, it should be a
> > > one shot (one version) tree from a linux-next point of view.
> > 
> > If he takes it, please remind me to remove the tree.
> 
> As of today, the final commit from this tree is merged, so it can be removed.

Thanks for letting me know ... I will remove it today.

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

      reply	other threads:[~2015-07-16  0:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02 23:23 [linux-next] please include init-v4.1-rc6 branch for v4.2 Paul Gortmaker
2015-06-03  3:39 ` Stephen Rothwell
2015-06-03 18:54   ` [linux-next] " Mark Brown
2015-06-03 21:41     ` Paul Gortmaker
2015-07-15 20:59   ` Paul Gortmaker
2015-07-16  0:06     ` Stephen Rothwell [this message]

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=20150716100619.33a65928@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=paul.gortmaker@windriver$(echo .)com \
    /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