--- Comment #15 from ---
We were a bit keen for a fix for this morning (29 Jan), so we went with Jim's
patch in trunk as it looked very conservative (extending tested behaviours to
Unix from Windows). I didn't see your patch at that point.

and we're now rolling that out across the pre-production environments today, 29

I can't really comment on the relative merits of either approach, so can you
give me a recommendation. Is this later patch either more robust or more
comprehensive than Jim's?  If you're making a strong recommendation, we will
see about pushing that version out to the pre-production environments as an
exceptional change, in advance of the next scheduled roll-out.

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to