From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: linux-arm-kernel@lists.infradead.org
Subject: ARM/ARM-SoC plans for v3.4 merge window
Date: Mon, 23 Jan 2012 11:49:02 +0000 [thread overview]
Message-ID: <20120123114902.GY1068@n2100.arm.linux.org.uk> (raw)
This is an outline of the plan for this cycle, up to the next merge
window, agreed between Olof and myself.
As Nicolas' idle changes weren't merged before the last merge window
opened, we have decided that Nicolas will resubmit his changes after
-rc1 (in other words, now) and they will be merged into both the
arm-soc and my trees.
I have at least one other patch which has a high 'will cause horrible
conficts' rating (the debug option rearrangement patch), so I'll be
including that for the arm-soc tree as well.
However, what this does mean is that Arnd, Olof, and myself will be
in for up to three months of merge hell unless people take account of
these changes.
Therefore, our plan is to publish this as a baseline, and we'd really
appreciate any development submitted after that baseline has been
established is based upon those changes and does not conflict with
them. That may mean you have to pull these changes into your tree
and merge them into your development work (and fix up any conflicts
there yourself.)
Once you've taken these changes into your tree, you must not rebase or
modify them. Changing those commits will cause all hell to break loose,
and we'll have to refuse merging your tree (otherwise we'll be in Linus'
sights for a roasting at gas mark 2 million.)
next reply other threads:[~2012-01-23 11:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 11:49 Russell King - ARM Linux [this message]
2012-01-24 9:50 ` ARM/ARM-SoC plans for v3.4 merge window Russell King - ARM Linux
2012-01-24 10:56 ` Will Deacon
2012-01-24 11:27 ` Russell King - ARM Linux
2012-01-24 11:45 ` Will Deacon
2012-01-26 21:23 ` Russell King - ARM Linux
2012-01-28 23:57 ` Olof Johansson
2012-01-30 10:08 ` Nicolas Ferre
2012-02-08 1:18 ` Olof Johansson
2012-02-08 11:52 ` Nicolas Ferre
2012-02-09 1:19 ` Olof Johansson
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=20120123114902.GY1068@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).