proper bug report procedure?

In response to bug #7249, mysqld_safe was changed (in 4.1.9) to fix the 
problem.  Unfortunately, the real problem was misunderstood, so the 
"fix" causes a separate but related problem that breaks mysqld_safe in 
some cases.  My thinking, then, was that this is still the same bug, 
modified by an incorrect fix.  With that in mind (and wanting to avoid 
the semi-rude response to duplicate bugs), I added a comment (4 days 
ago) to the bug explaining the problem and offering a fix.  My comment 
doesn't seem to have been noticed, as there's been no response.  Am I 
simply being too impatient, or should I have submitted this as a 
separate bug?

Possibly the problem lies in the bug status -- No Feedback.  The 
message from the bugs system invites me to comment and "change the 
status of the bug back to 'Open', but as I am neither a developer nor 
the original poster, I have no power to change the status.  I can 
imagine the developers are watching for bugs with an open status.  What 
is the correct thing to do in this case?  That is, in general, how does 
one add a comment that will be noticed to a bug without changing the 
status?

Michael

-- 
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe:    http://lists.mysql.com/[email protected]