[Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

[Jason Cooper]

On Mon, Jul 29, 2013 at 10:49:40AM -0700, Greg KH wrote:
> On Mon, Jul 29, 2013 at 01:36:19PM -0400, Jason Cooper wrote:

> > Would it be possible for patches developers think are candidates for
> > -stable inclusion be sent to the stable mailinglist before they are in
> > tree?  Then, if the stable maintainers feel it's appropriate for
> > -stable, they'll give and 'Acked-by: <...> # v3.10.x'.  At that point,
> > the subsystem maintainer can put it in a branch to be pulled into Linus'
> > tree and then into the appropriate -stable tree.
> 
> I personally don't have the time to review such things to provide an
> Acked-by: line.  

Right, I was referring to the whole -stable team.

But it's a moot point now, Paul explained in detail how my idea was Not
Good (tm).  ;-)

> I rely on the subsystem maintainer to make the
> judgement call first (i.e. usually, if they think it should be in the
> stable tree, and it matches the stable tree rules, I accept it.)
> 
> Making me ack each patch before it goes to Linus would increase my
> workload a lot, and slow down the flow of patches to Linus, neither of
> which would be a good thing from my point of view :)

Agreed.

thx,

Jason.