From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL V2 1/4] ARM: Kirkwood: DT bindings for v3.7
Date: Wed, 19 Sep 2012 13:59:40 +0000 [thread overview]
Message-ID: <201209191359.40856.arnd@arndb.de> (raw)
In-Reply-To: <20120918172426.GL5469@titan.lakedaemon.net>
On Tuesday 18 September 2012, Jason Cooper wrote:
> Ok, I'm still mastering the art of branch dependencies. The acceptance
> of Gregory's cache-l2x0 series is holding up everything else.
> Rightfully so, rmk has some issues with it.
>
> However, in my pullrqs and in my branch merging I treated it as a
> dependency for everything that came after it (pr 1,2,3,4). I'd like to
> undo that now to get things moving. The dependency was not strictly
> necessary, I was simply trying to achieve an ordering of branches.
>
> The only way I know to do this is to redo my branches and republish.
> Basically, I would remove Gregory's patches and the dependency on 'arm:
> cache-l2x0' from pullrq [1/4] Kirkwood DT bindings.
Right, makes sense.
> Obviously, this would break things for folks tracking my branches.
> Hopefully anyone crazy enough to track my branches is competent enough
> rebase onto the new branches. Even still, I don't want to mess anyone up.
>
> I think the benefits of getting these patches in for this merge window
> outweigh a onetime breaking of my branches. Is there anything I'm not
> considering before I do this?
>
> I'll do the work now, but hold off on pushing or sending new pullrq's
> for a day or two or until I hear from you guys.
My rule is normally that I treat any branches coming from subarchitecture
maintainers as unstable until they are merged into arm-soc.
If you haven't promised anyone to keep your branches stable, I see no
problem with rebasing them to avoid the dependency.
Arnd
next prev parent reply other threads:[~2012-09-19 13:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 0:11 [GIT PULL] Kirkwood: board changes for v3.7 Jason Cooper
2012-09-05 4:34 ` Olof Johansson
2012-09-05 23:44 ` Jason Cooper
2012-09-05 23:58 ` Olof Johansson
2012-09-10 5:31 ` Jason Cooper
2012-09-10 5:40 ` [GIT PULL V2] ARM: cache-l2x0 for rmk's tree Jason Cooper
2012-09-10 5:48 ` [GIT PULL V2 1/4] ARM: Kirkwood: DT bindings for v3.7 Jason Cooper
2012-09-13 5:30 ` Olof Johansson
2012-09-18 17:24 ` Jason Cooper
2012-09-19 13:59 ` Arnd Bergmann [this message]
2012-09-10 5:57 ` [GIT PULL V2 2/4] ARM: Kirkwood: boards " Jason Cooper
2012-09-10 6:03 ` [GIT PULL V2 3/4] ARM: Kirkwood: cleanup " Jason Cooper
2012-09-10 6:07 ` [GIT PULL V2 4/4] ARM: Kirkwood: defconfig changes " Jason Cooper
2012-09-21 19:41 ` [GIT PULL V3 1/5] ARM: Kirkwood: address decoding change " Jason Cooper
2012-09-22 5:29 ` Olof Johansson
2012-09-22 7:30 ` Arnd Bergmann
2012-09-22 8:20 ` Thomas Petazzoni
2012-09-21 19:46 ` [GIT PULL V3 2/5] ARM: Kirkwood: DT changes " Jason Cooper
2012-09-22 5:11 ` Olof Johansson
2012-09-22 13:21 ` Jason Cooper
2012-09-21 19:48 ` [GIT PULL V3 3/5] ARM: Kirkwood: board " Jason Cooper
2012-09-21 19:57 ` [GIT PULL V3 4/5] ARM: Kirkwood: cleanup " Jason Cooper
2012-09-22 1:48 ` [GIT PULL V4 4a/5] " Jason Cooper
2012-09-22 1:53 ` [GIT PULL V4 4b/5] ARM: Kirkwood: platform_data " Jason Cooper
2012-09-22 5:17 ` [GIT PULL V3 4/5] ARM: Kirkwood: cleanup " Olof Johansson
2012-09-22 13:31 ` Jason Cooper
2012-09-21 19:58 ` [GIT PULL V3 5/5] ARM: Kirkwood: defconfig changes " Jason Cooper
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=201209191359.40856.arnd@arndb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.