If you're not a contributor and don't have commit access, you can stop reading now.
Let me remind you the last time you put yourself in this precise situation: - Damn I have an undisclosed number of engineers waiting for me to fix the tree and Nicolas is in possession of the squeaky bat! The try slaves already sent 30 failures emails! (not that I personally care) What do I need to do? Situation you reached by following this good old recipe: 1. Change stuff. 2. Send for review. 3. Your reviewer misses the obvious FAIL(tm) in your change and rubber stamp lgtm. 4. Commit bad stuff. 5. Walk away. Here's the recipe to fix things: $revert 123 -c -r [EMAIL PROTECTED] -m "I broke the build. Blame my reviewer." Where 123 is the magic number for all the failing changes. I heard 42 works too. All other flags are optional. Now I could start a long and dull email explaining all the possible ways to use this nifty little tool that has only one purpose but hey, I know you're smarter than me and will just execute 'revert --help'. But still, I'll add that if you revert someone else's change, by default he'll be the reviewer so no need to specify --reviewers. Thanks, M-A --~--~---------~--~----~------------~-------~--~----~ v8-users mailing list [email protected] http://groups.google.com/group/v8-users -~----------~----~----~----~------~----~------~--~---
