Nick, you say you could not reproduce the bug using version 8.2.5h-667-g971dc4, but you did with version 8.2.5h-888-g798bb8d. Just out of curiosity: does the '888' in '8.2.5h-888-g798bb8d' is a number that is incremented chronologically? If this is correct (I'm not familiar with this at all), FWIW, the bug was not caused only by the patch '8.2.5h-888-g798bb8d', since I observed it also with version 8.2.5h-94-g91175a.
FC On Wed, Apr 9, 2014 at 3:52 PM, Nick Dokos <ndo...@gmail.com> wrote: > Nick Dokos <ndo...@gmail.com> writes: > > > > > Starting from release_8.2.5h-888-g798bb8d (this was latest as of this > > morning) and reverting the above commit fixes Fletcher's problem. > > > > Just to be clear: I'm *not* advocating that the commit be reverted. > I used the revert just to confirm that something in that patch caused > the problem that Fletcher observed. > > Nick > > >
