Em Segunda-feira 09 Novembro 2009, às 15:19:17, você escreveu: > 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?
No.
Two commit SHA-1 are very useful for us. The closer they are to one another,
the better.
They are the next best thing to pointing the exact SHA-1 that broke anything.
Even better than that, it's sending a QtTest-based testcase :-)
--
Thiago Macieira - thiago.macieira (AT) nokia.com
Senior Product Manager - Nokia, Qt Development Frameworks
Sandakerveien 116, NO-0402 Oslo, Norway
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Qt4-preview-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt4-preview-feedback
