On Mon, Apr 24, 2017 at 10:29:02AM -0700, Olof Johansson wrote:
> On Mon, Apr 24, 2017 at 9:17 AM, Linus Walleij <linus.walleij@linaro.org> wrote:

> > One thing he does is queue an immutable topic branch, announce it and
> > let all affected subsystems pull it in, so that we (e.g. GPIO) can then
> > refactor or apply local fixes in "our" subsystem from that point, even during
> > the development cycle. It is pretty neat.

> Yeah, Lee has been doing a good job there (even though we always
> double-check about immutable branches to make the producer aware that

Yeah, I do the same thing where that comes up (mainly for regulator and
sometimes regmap).  Seems to work pretty well.

> we've picked it up). The clk maintainers (Mike/Stephen) have been
> doing a good job too where they tend to apply patches on a per-driver
> branch that they keep immutable.

That's what I do as well.  It's especially helpful if you discover a
need to do a cross merge after things have been applied, it means that
you probably already have something fairly sensible to send to the other
maintainers involved and don't need to rebase things or duplicate
commits.  Before I started doing this those things were always painful,
now I just need to sign a tag.