Imagine some program and a number of changes. If none of these changes is applied ("yesterday''), the program works. If all changes are applied (`"today''), the program does not work. Which change is responsible for the failure? We present an efficient algorithm that determines the minimal set of failure-inducing changes. Our delta debugging prototype tracked down a single failure-inducing change from 178,000 changed GDB lines within a few hours.