Matthias Hopf writes:
Now, at the end of this week, 3 possibilities arise:
- We release now, with the regression. I think that not too many people are actually affected, so it is an option.
Wouldn't kill us - the work around (restart X) is easy, and if a release causes the bug to bite more people, you'll get more info about how to fix it. It's unlikely I'll have a chance to really run the git bisect process to ground today, but will try knowing you've got a deadline. Worse comes to worst, I'll also be on the road next week, and airplane time makes great debugging time (provided I get a local git repository ondisk before leaving :) -- Alec Habig, University of Minnesota Duluth Physics Dept. habig@neutrino.d.umn.edu http://neutrino.d.umn.edu/~habig/ -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org