From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung S5P for 2.6.38 merge window
Date: Sat, 15 Jan 2011 13:44:16 +0000 [thread overview]
Message-ID: <20110115134416.GB15996@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110115132955.GA15996@n2100.arm.linux.org.uk>
On Sat, Jan 15, 2011 at 01:29:55PM +0000, Russell King - ARM Linux wrote:
> On Thu, Jan 13, 2011 at 02:30:01PM +0900, Kukjin Kim wrote:
> > Hi Russell,
> >
> > Please pull Samsung S5P updates from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> > for-rmk
> >
> > These things are for 2.6.38.
>
> This looks very large. I really considered not merging this due to:
>
> 1. possibly conflicts with Lennert's irq_data conversion patches.
>
> 2. It's not right to push large quantities of code into mainline towards
> the end of the merge window. You should have everything prepared
> that you want to send before the merge window opens.
>
> In future, please have your tree ready for merging *before* the merge
> window opens and aim to get the bulk in preferably before, at the latest
> during the first week.
And... merging this kills off the ability to get a sane diffstat out
of git for my devel-stable branch due to multiple common ancestors.
We'll see what Linus says on this - but there are three outcomes:
1. Linus responds quickly, and wants his tree merged into mine before
he pulls (Linus isn't generally a fan of last minute cross-tree
merging.)
2. Linus doesn't respond before the merge window closes, and I leave the
tree as is, which means no pull request being sent and therefore it
doesn't make mainline.
3. Linus doesn't respond before the merge window closes, I decide to
drop your tree, and send a pull request which Linus actions.
Realistically, it's (1) or (3).
This is yet another reason to get your tree ready before the merge
window opens.
next prev parent reply other threads:[~2011-01-15 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 5:30 [GIT PULL] Samsung S5P for 2.6.38 merge window Kukjin Kim
2011-01-15 13:29 ` Russell King - ARM Linux
2011-01-15 13:44 ` Russell King - ARM Linux [this message]
2011-01-17 0:54 ` Kukjin Kim
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=20110115134416.GB15996@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