Hi Juliet, Just a friendly suggestion:
When going through multiple revisions, you could consider tagging patches as PATCHv22 (git format-patch -v22 ...) and/or adding some revision history in the summary (see commit 7be0c99c75589b4810160772a79d7dc088bc8f0e). It should minimise the confusion of "which version is this/did it fix issue X" and hopefully ease your reviewers. -Emil _______________________________________________ Piglit mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/piglit
