Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1182
Merging if there is no more discussions
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this featur
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1182
Tested, LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1182
@corneadoug from what you say, it's still not clear what's the plan with
this one.
I do not think it was rebased, where `rebased = git rebase` - that way all
the commits would show up AFTER t
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1182
#1171 is merged already, and this one has been rebased
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1182
So what is the consensus, shall we actually *rebase* this one on master and
merge, or just close, as soon as #1171 is merged?
---
If your project is set up for it, you can reply to this email and hav
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1182
@Leemoonsoo Yes, I agree, we should merge #1171.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not ha
