Deputy maintainer for powerpc

I'm going to be on vacation for the next two weeks, and it looks
highly likely that Linus will open the 2.6.27 merge window during that
time, so I'm appointing Ben Herrenschmidt as my deputy maintainer.
During the next two weeks, he'll be the person collecting together any
further powerpc-related commits that need to go upstream, and sending
pull requests to Linus as necessary.

This is the start of a longer-term transition which will ultimately
result in me handing over the powerpc architecture maintainership to
Ben.  Because of various work commitments, this will be a gradual
transition taking probably around 6 months.

Paul.

On Jul 4, 2008, at 1:02 AM, Paul Mackerras wrote:

I'm going to be on vacation for the next two weeks, and it looks
highly likely that Linus will open the 2.6.27 merge window during that
time, so I'm appointing Ben Herrenschmidt as my deputy maintainer.
During the next two weeks, he'll be the person collecting together any
further powerpc-related commits that need to go upstream, and sending
pull requests to Linus as necessary.

This is the start of a longer-term transition which will ultimately
result in me handing over the powerpc architecture maintainership to
Ben.  Because of various work commitments, this will be a gradual
transition taking probably around 6 months.

Paul.

Ben, Do you have a tree that you'll be using to collect things in?

- k

On Mon, 7 Jul 2008 09:44:31 -0500
Kumar Gala [off-list ref] wrote:

On Jul 4, 2008, at 1:02 AM, Paul Mackerras wrote:

quoted

I'm going to be on vacation for the next two weeks, and it looks
highly likely that Linus will open the 2.6.27 merge window during that
time, so I'm appointing Ben Herrenschmidt as my deputy maintainer.
During the next two weeks, he'll be the person collecting together any
further powerpc-related commits that need to go upstream, and sending
pull requests to Linus as necessary.

This is the start of a longer-term transition which will ultimately
result in me handing over the powerpc architecture maintainership to
Ben.  Because of various work commitments, this will be a gradual
transition taking probably around 6 months.

Paul.

Ben, Do you have a tree that you'll be using to collect things in?

I hope it's the same tree for this merge window.

In the future, I hope the semantics of the various branches of the
new tree either stays the same, or comes with a detailed description of
what branch means what (assuming there is a new tree at some point).

josh

On Mon, 2008-07-07 at 09:44 -0500, Kumar Gala wrote:

On Jul 4, 2008, at 1:02 AM, Paul Mackerras wrote:

quoted

I'm going to be on vacation for the next two weeks, and it looks
highly likely that Linus will open the 2.6.27 merge window during that
time, so I'm appointing Ben Herrenschmidt as my deputy maintainer.
During the next two weeks, he'll be the person collecting together any
further powerpc-related commits that need to go upstream, and sending
pull requests to Linus as necessary.

This is the start of a longer-term transition which will ultimately
result in me handing over the powerpc architecture maintainership to
Ben.  Because of various work commitments, this will be a gradual
transition taking probably around 6 months.

Paul.

Ben, Do you have a tree that you'll be using to collect things in?

I've setup a tree on kernel.org yes, but there's nothing useful in
it yet (it has 3 branches, master, merge and next, but they are
currently pointing to the exact same spot as Paul's).

I've started collecting things yesterday and sending comments, I'll
push some new stuff out today or tomorrow. Mostly been "training" with
git and patchwork so far :-)

Ben.

On Mon, 2008-07-07 at 15:25 -0400, Josh Boyer wrote:

quoted

Ben, Do you have a tree that you'll be using to collect things in?

I hope it's the same tree for this merge window.

It's in a different place but it's essentially the same tree (ie, I
pulled in paulus branches and my current heads are identical, at least
until I start adding things to it).

In the future, I hope the semantics of the various branches of the
new tree either stays the same, or comes with a detailed description
of what branch means what (assuming there is a new tree at some
point).

Branches are the same, master,merge and next (the only subtle difference
is that my next branch is called just "next" and not "powerpc-next").

Ben.