From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] GIC DT binding support
Date: Thu, 20 Oct 2011 16:08:32 -0500 [thread overview]
Message-ID: <4EA08DD0.1090706@gmail.com> (raw)
In-Reply-To: <20111020185612.GD21648@n2100.arm.linux.org.uk>
Russell,
On 10/20/2011 01:56 PM, Russell King - ARM Linux wrote:
> On Thu, Oct 20, 2011 at 12:09:03PM -0500, Rob Herring wrote:
>> highbank/soc doesn't build. It needs Russell's l2x0 and io branches.
>> l2x0 has been rebased recently, but the io branch seems to be stable
>> (but not published externally).
>
> Actually, l2x0 _hasn't_. Let's be clear about what happened. A load
> of patches were all merged into the 'misc' branch over time, containing
> multiple different subjects. At the time they were merged there was
> no clear separate line of development of each sub-system, so they
> just ended up in a common branch without any particular ordering or
> grouping.
>
> People wanted to base work on a select few of those commits. Rather
> than having the entire set of commits merged into various peoples trees,
> many of which have nothing to do with what they were working on, I
> split various commits out of the 'misc' branch and created a set of
> more fine-grained topic branches.
>
> That is arguably not rebasing - it is re-committing, in such a way that
> those parts can then be frozen, stabilized and published without
> unintended dependencies. That's got to be a good thing.
Understood, but from a git perspective the commit ids have changed.
While git can deal with trivial re-commits like this, my understanding
is that should be avoided for upstream merges. Otherwise, I could just
cherry-pick them and re-commit them in my tree.
Ultimately, the people working off of those branches do need them to be
stable to merge their branches. So are you saying your l2x0 branch
(91c2ebb90b1890abc648ba9dec5608cbc97e1cb9) is now stable? Can you
publish it as a branch. iMX6Q is also dependent on it.
Rob
next prev parent reply other threads:[~2011-10-20 21:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 3:01 [GIT PULL] GIC DT binding support Rob Herring
2011-10-14 3:18 ` Shawn Guo
2011-10-18 9:53 ` Domenico Andreoli
2011-10-18 14:50 ` Rob Herring
2011-10-18 14:58 ` Domenico Andreoli
2011-10-18 15:10 ` Rob Herring
2011-10-20 12:48 ` Shawn Guo
2011-10-20 12:50 ` Russell King - ARM Linux
2011-10-20 13:07 ` Arnd Bergmann
2011-10-20 14:34 ` Rob Herring
2011-10-20 16:12 ` Arnd Bergmann
2011-10-20 17:09 ` Rob Herring
2011-10-20 18:56 ` Russell King - ARM Linux
2011-10-20 21:04 ` Arnd Bergmann
2011-10-21 18:33 ` Russell King - ARM Linux
2011-10-21 19:31 ` Arnd Bergmann
2011-10-21 22:25 ` Russell King - ARM Linux
2011-10-20 21:08 ` Rob Herring [this message]
2011-10-20 21:15 ` Russell King - ARM Linux
2011-10-20 21:17 ` Arnd Bergmann
2011-10-21 8:51 ` Arnd Bergmann
2011-10-21 20:09 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2011-10-24 21:38 Rob Herring
2011-10-28 21:17 ` Rob Herring
2011-10-30 22:39 ` Arnd Bergmann
2011-10-31 0:31 ` Arnd Bergmann
2011-10-31 1:45 ` Rob Herring
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=4EA08DD0.1090706@gmail.com \
--to=robherring2@gmail.com \
--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).