[Ksummit-2012-discuss] [ATTEND] stable kernel stuff and grumpy maintainers [bisection/rebase/-next]

Steven Rostedt rostedt at goodmis.org
Thu Jun 21 14:32:09 UTC 2012


On Thu, 2012-06-21 at 09:22 -0500, Jason Wessel wrote:
> On 06/21/2012 09:05 AM, Steven Rostedt wrote:
> > On Thu, 2012-06-21 at 08:59 -0500, Jason Wessel wrote:
> > 
> >> 2) The maintainers with non-reversible trees
> >>
> >>   * Having a maintainer who can get a 24 hour period before etching
> >>     something in stone in non-reversible branches would be a world
> >>     better than what we have today.
> > 
> > I believe that this is exactly what tip does today.
> > 
> 
> 
> I could have sworn you stated that tip gets a build failure, you add
> another patch etc... At the point in time it is in tip, isn't it
> already in stone and you have recorded a point that is not actually
> bisectable for some number of patches?

I meant, tests are run for 24 hours locally in Ingo's test suite before
he pushes it to the public repo. He does not push out as soon as he does
a pull.

-- Steve

> 
> One of the key points here was trying to improve bisectability (and
> also as a direct result the general input quality).





More information about the Ksummit-2012-discuss mailing list