-1 (non-binding) force pushes are extremely disruptive. there's no way to know who's updated their local git repo to include these changes since the commit went in. if a merge commit is so disruptive that we need to subject folks to the inconvenience of a force push then we should have more tooling in place to avoid them (like client side git hooks for all committers).
On Thu, Jul 5, 2018 at 4:37 PM, Subru Krishnan <su...@apache.org> wrote: > Folks, > > There was a merge commit accidentally pushed to trunk, you can find the > details in the mail thread [1]. > > I have raised an INFRA ticket [2] to reset/force push to clean up trunk. > > Can we have a quick vote for INFRA sign-off to proceed as this is blocking > all commits? > > Thanks, > Subru > > [1] > http://mail-archives.apache.org/mod_mbox/hadoop-yarn-dev/201807.mbox/%3CCAHqguubKBqwfUMwhtJuSD7X1Bgfro_P6FV%2BhhFhMMYRaxFsF9Q%40mail.gmail.com%3E > [2] https://issues.apache.org/jira/browse/INFRA-16727 -- busbey --------------------------------------------------------------------- To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
