On Monday 09 November 2009 10:18:49 Olivier Goffart wrote: > http://bugreports.qt.nokia.com/browse/QTBUG-5588
Sorry should have thought of that myself. Thanks for taking care of this. > Note that date are meaningless to us. [...] > Only sha1 are meaningfull. I'll keep that in mind for the future. IMHO that also implies that giving you two commit hashes kinda as a specific range where the regression/bug was introduced won't help much because it is not easily apparent which private branches have been pushed to the public repository in which order and what really lies between those two hashes. So the only real help is doing something like a git bisect and point you right to the actual commit that caused the regression/bug. Am I right with that? > > 2] krunner 4.3.3 crashing > I cannot reproduce this crash. But this is maybe because my checkout of > Qt is not as recent. (i am using my team branch, and last merge was on > friday) > > Do you have a backtrace? Unfortunately not. I was in a hurry to get everything in a working state again, so I forgot to take the backtrace. Sorry. If it hasn't been fixed by now, you will run into it as soon as your branch gets updated or it was just bad timing with my pull. So long, matthias _______________________________________________ Qt4-preview-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt4-preview-feedback
