From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jiri Kosina <jikos@jikos.cz>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: please don't start adding v3.21 stuff yet
Date: Thu, 19 Feb 2015 07:44:31 +1100 [thread overview]
Message-ID: <20150219074431.77e56ef8@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]
Hi Jiri,
From my daily release notes:
"Please do not add any material destined for v3.21 to your linux-next
included trees until after v3.20-rc1 has been released."
Commit 38e0e413ca1d ("Merge branch 'for-3.21/logitech' into for-next"),
commit e0ab74fe569d ("Merge branch 'for-3.21/rmi' into for-next"),
commit ee2de8fc6c18 ("Merge branch 'for-3.21/genius' into for-next")
(though this last contains what looks like a fix).
:-(
Also, at some point you might want to reset your tree to Linus' to get
rid of all those (now useless) old merge commits.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2015-02-18 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 20:44 Stephen Rothwell [this message]
2015-02-18 20:53 ` linux-next: please don't start adding v3.21 stuff yet Jiri Kosina
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=20150219074431.77e56ef8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jikos@jikos.cz \
--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