Can I get a committer to mark this bug as blocking 6.4-RELEASE ?

[Jo Rhett]

On Dec 1, 2008, at 12:25 PM, Xin LI wrote:
> What I proposed is, to *narrow down* the problem so we can diagnose
> further, since nobody has idea at the moment about how the problem  
> was,
> we do need to have further information, or, to get the whole 6.3->6.4
> diff reviewed, which is (in my opinion) not an optimal use of
> developers' time.


I got your request at the beginning of a vacation period where I was  
out of town.  I had explicitly requested that 6.4 be blocked for this  
issue.  I didn't think that "just my problem" would be enough to hold  
it up, but I apparently never even considered that -REL would happen  
without even responding to my request.

Since nobody had responded to my request, and several posts had gone  
out about more testing for 7.1 (which had the same loader and the same  
problems) I assumed that 6.4 was similarly delayed.  Had anyone said  
you needed this information pronto I would have canceled my  
Thanksgiving plans and spent the day in the lab testing this for you.

For that matter, I had already pulled a diff of 6.3 to 6.4 and was  
working my way through it trying to find the relevant parts.  If you  
would have identified the relevant portions, I would have happily  
tried backing out some of the changes on a per-component basis to  
figure it out.

In short, tell me what you wanted/needed, and I would have done it ASAP.

It's apparently irrelevant now.

-- 
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source  
and other randomness