On Nov 29, 2008, at 11:16 PM, chromatic wrote:
If you're continuing to bisect to the offending patch, you don't
need to
update the ticket with ranges is useful. If you can't narrow it
down further
that's one thing, but if you haven't hit the limit of what you can
find, I
don't need these mini-status updates to help me fix it.
I haven't hit the limit of what I can find -- but that's because the
machine on which I observed this failure is slow and I can't do that
many bisects in one session. So posting where I leave off at night
may permit someone else to pick up the bisecting process and work on
a solution.
Thank you very much.
kid51
