AFAIK all the reception desks have pumps. Not sure if they have a
needle though (the type used for inflating basketballs / volleyballs - you
might try the gym in 40, think they have one...)

On Tue, Dec 2, 2008 at 6:07 PM, Ben Goodger (Google) <[EMAIL PROTECTED]>wrote:

>
> On a slightly related note, the Powerpuff Girls squeakbat has a leak
> and has deflated. Does anyone @Google have a bicycle repair kit? If so
> let me know and we will figure out how to repair it.
>
> -Ben
>
> On Tue, Dec 2, 2008 at 6:03 PM, Marc-Antoine Ruel <[EMAIL PROTECTED]>
> wrote:
> > 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:
> >
> > Change stuff.
> > Send for review.
> > Your reviewer misses the obvious FAIL(tm) in your change and rubber stamp
> > lgtm.
> > Commit bad stuff.
> > 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to