On Fri, 20 Jan 2006, Kenneth Zadeck wrote:
> I would like permission to revert Zdenek's patch for a few days.  There
> is nothing wrong with zdenek's patch, pe se, but it excercises a part of
> df that should work but does not.


I'm going to make an executive decision on this one, to restore bootstrap
immediately.  I agree that Zdenek's patch be reverted for a few days
without prejudice.  Both patch submitters followed the rules of bootstrap
and regression test, but a bad (unforetestable) interaction occurred
between the two.  It turns out that it was the Kenny's DF changes at
fault, that contain paths that weren't fully tested with his changes
alone.  Zdenek's patch is innocent, but reliant on this problematic
functionality.

Normally, we'd allow 48 hours of shouting before fixing the tree.
But I think we agree that in the case "the mid-air collision" needs
to be resolved by Kenny, and his request for a short-term work around
carries some weight.  With no shame on the killloop merge, I suspect we
should back it out, as it is mostly new functionality, whilst Kenny's
patch also contained bug-fixes, and is therefore probably the more stable
of the two bits when applied independently.

I hope this is satisfactory to anyone.  The judge's decision is final
modulo an over-ruling by Mark or the SC.  This gets the tree back to
bootstrap land, and allows the rest of GOMP to be merged etc... at a
busy point in the GCC lifecycle.

The clock is ticking for Kenny.  I propose a reverse 48 hour rule
where we reinstate Zdenek's patch on Monday, either by fixing DF
by then or by reverting the DF changes.  i.e. swap one of the clashing
patches for the other.

My apologies to everyone for any inconvenience.  Many thanks to Dan
and H-P for investigating the problem on IRC.

Roger
--
Roger Sayle,                         E-mail: [EMAIL PROTECTED]
OpenEye Scientific Software,         WWW: http://www.eyesopen.com/
Suite 1107, 3600 Cerrillos Road,     Tel: (+1) 505-473-7385
Santa Fe, New Mexico, 87507.         Fax: (+1) 505-473-0833

Reply via email to