[Ksummit-2013-discuss] [ATTEND] maintainer hierarchy vs. the release process

[John W. Linville]

On Sat, Jul 13, 2013 at 07:36:31AM -0700, H. Peter Anvin wrote:
> On 07/12/2013 11:53 AM, John W. Linville wrote:
> > On Fri, Jul 12, 2013 at 11:44:01AM -0700, H. Peter Anvin wrote:
> > 
> >> One major advantage is that it forces us to write a general description
> >> for each topic.  This is pretty simple with a smallish number of
> >> patches, but for a single x86 pull request it would be meaningless.
> >>
> >> I understand Linus' normal workflow is to pull in the x86 pull requests
> >> (minus any he might reject) and then do testing on the whole thing, though.
> > 
> > While x86 may merit that level of special attention, I suspect that
> > many other arches or random features would not.
> > 
> 
> Now, this model was explicitly requested from us by Linus.
> 
> There is actually a very simple way a top-level maintainer can find out
> how Linus would like that particular top-level maintainer to push... he
> can simply drop an email and ask (if there is no reply, it probably
> means keep doing what you're doing...)

True.  Nevertheless, it can he helpful to bang-out a general conclusion
as to what might work and (with Linus in the discussion) what Linus
might like before proposing umpteen custom solutions.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville at tuxdriver.com			might be all we have.  Be ready.