[GitHub] zeppelin issue #1574: ZEPPELIN-1595. Make ZeppelinContext extensible

2017-02-04 Thread wesm
Github user wesm commented on the issue: https://github.com/apache/zeppelin/pull/1574 Whatever you did generated a merge commit. The proof is right there -- a rebate or amend would not have two parents --- If your project is set up for it, you can reply to this email and have your

[GitHub] zeppelin issue #1574: ZEPPELIN-1595. Make ZeppelinContext extensible

2017-02-04 Thread wesm
Github user wesm commented on the issue: https://github.com/apache/zeppelin/pull/1574 @felixcheung it looks like these builds were triggered by a merge on a different branch. see for example https://github.com/apache/zeppelin/commit/e259feacf78770b5dc412c0642216acdce17008f

[GitHub] zeppelin issue #1574: ZEPPELIN-1595. Make ZeppelinContext extensible

2017-02-04 Thread wesm
Github user wesm commented on the issue: https://github.com/apache/zeppelin/pull/1574 In trying to investigate why the Apache Travis CI build queue is extremely backlogged, I found many build requests from this particular PR in https://travis-ci.org/apache/zeppelin/pull_requests