Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1674
Let's close. Since it's outdated.
---
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
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1674
Sounds good, let's take care of small parts first, and then rebase and
merge this guys in a bulk!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1674
@bzz We can rebase and merge smaller PRs first like
https://github.com/apache/zeppelin/pull/1668 and #1339 you mentioned.
I will rebase #1668 first.
---
If your project is set up f
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1674
AFAIK there is going to be at least few other changes that will most
probably affect this PR i.e #1674 and #1339 - may be we should prioritize
those smaller ones, and then rebase\merge this guy?
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1674
\cc @bzz for reviewing this issue. (related to
https://github.com/apache/zeppelin/pull/1662)
thanks!
---
If your project is set up for it, you can reply to this email and have your
reply
