linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for May 16
Date: Mon, 16 May 2016 14:58:20 +1000	[thread overview]
Message-ID: <20160516145820.6eb5e38a@canb.auug.org.au> (raw)
In-Reply-To: <20160516145614.2a06989b@canb.auug.org.au>

Hi all,

I forgot to say:  Please do not add any v4.8 destined material to your
linux-next included branches until after v4.7-rc1 has been released.

-- 
Cheers,
Stephen Rothwell

  reply	other threads:[~2016-05-16  4:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16  4:56 linux-next: Tree for May 16 Stephen Rothwell
2016-05-16  4:58 ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-16  2:33 Stephen Rothwell
2022-05-16 10:57 Stephen Rothwell
2019-05-16  3:59 Stephen Rothwell
2018-05-16  8:02 Stephen Rothwell
2017-05-16  1:21 Stephen Rothwell
2014-05-16  7:25 Stephen Rothwell
2013-05-16  5:08 Stephen Rothwell
2012-05-16 10:14 Stephen Rothwell
2011-05-16  5:10 Stephen Rothwell
2008-05-16  8:15 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=20160516145820.6eb5e38a@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@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).