Hipchat did the trick, good idea Chris. We got some quick action on INFRA-11236, and the current set of branch-*s are now disabled.
So, from now on if you create a new branch-*, please also file an INFRA ticket to get force push disabled. Best, Andrew On Tue, May 3, 2016 at 4:00 PM, Chris Nauroth <cnaur...@hortonworks.com> wrote: > Hello Andrew, > > I always see multiple members of the infra team in their HipChat channel. > I've found that going in there and mentioning your JIRA issue is the most > effective way to get their attention if you want to request prioritization. > > http://infra.chat/ > > --Chris Nauroth > > > > > On 5/3/16, 3:45 PM, "Andrew Wang" <andrew.w...@cloudera.com> wrote: > > >Does anyone have any pull with INFRA? I ping'd INFRA-11236 but it's > >unassigned and been dormant for a while. > > > >On Tue, May 3, 2016 at 3:07 PM, Allen Wittenauer <a...@apache.org> wrote: > > > >> > >> > >> Just a heads up that I accidentally forced push over branch-2 > >>and > >> branch-2.8 (in the process of pushing a feature branch) around 10am PT > >>this > >> morning that dropped several commits. I have since reset us back to > >>those > >> git refs. If anything has been committed since then, please recommit. > >> Sorry for the problems! > >> > >> Thanks to Jason Lowe for pointing out my mistake! > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > >> For additional commands, e-mail: common-dev-h...@hadoop.apache.org > >> > >> > >
