From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] GIC DT binding support
Date: Fri, 21 Oct 2011 21:31:46 +0200 [thread overview]
Message-ID: <2460374.AAkEFv9LMo@wuerfel> (raw)
In-Reply-To: <20111021183352.GI21648@n2100.arm.linux.org.uk>
On Friday 21 October 2011 19:33:52 Russell King - ARM Linux wrote:
> On Thu, Oct 20, 2011 at 11:04:35PM +0200, Arnd Bergmann wrote:
> > I'm not sure if I used the intended process to get at those branches.
> > Since they are not published on ftp.arm.linux.org.uk as separate branches,
> > I looked at the big merge changeset in the for-next branch and recreated
> > the branches I needed, which feels like I'm doing something that wasn't
> > your intention. Is there a better way?
>
> The best way is to say "Hey, my work depends on X, Y, Z" and I'll see
> what can be done to make them stable and say whether they are ripe
> for that yet (or, eg, whether they're waiting for peoples acks.)
>
> It's actually what I documented a while ago at
> http://www.arm.linux.org.uk/developer/git-arm.php
Ok, that is a very useful documentation, but the part I still don't
understand is how I should get the commit ID of the stable branches.
I noticed that you are publishing an l2x0 branch now, in addition
to the pm and smp branches that were already there the last time
I looked, but you don't publish the gpio, io and debug branches
that I have pulled into the arm-soc/next-soc branch because imx6 and
highbank depend on them.
Does that mean you don't consider the latter three branches stable
yet, or does it just mean they are stable but you had no reason
to publish them?
Arnd
next prev parent reply other threads:[~2011-10-21 19:31 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 [this message]
2011-10-21 22:25 ` Russell King - ARM Linux
2011-10-20 21:08 ` Rob Herring
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=2460374.AAkEFv9LMo@wuerfel \
--to=arnd@arndb.de \
--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