You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by OutOfBedlam <gi...@git.apache.org> on 2016/06/12 13:12:14 UTC
[GitHub] zeppelin pull request #1000: typo
GitHub user OutOfBedlam opened a pull request:
https://github.com/apache/zeppelin/pull/1000
typo
### What is this PR for?
bin/zeppelin.sh - typo fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Solution-Global/zeppelin master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1000.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1000
----
commit b0d4986202bd2c91c2d6efd7fbc4c742186cc870
Author: Kwon, Yeong-Eon <ha...@gmail.com>
Date: 2016-06-12T12:49:55Z
typo
----
---
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 if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin pull request #1000: typo
Posted by OutOfBedlam <gi...@git.apache.org>.
Github user OutOfBedlam closed the pull request at:
https://github.com/apache/zeppelin/pull/1000
---
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 if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #1000: typo
Posted by corneadoug <gi...@git.apache.org>.
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1000
@OutOfBedlam Could you reverse the last commit? I can't merge it now.
Also, when doing a PR, it is better to use a branch instead of master
---
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 if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #1000: typo
Posted by corneadoug <gi...@git.apache.org>.
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1000
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 feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #1000: typo
Posted by bzz <gi...@git.apache.org>.
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1000
Last commit needs to be removed by using git interactive rebase, as it's been taken care of under #1009
It would also be great to have more descriptive PR title like `Fix typo in bin/zeppelin.sh`
---
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 if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #1000: typo
Posted by jongyoul <gi...@git.apache.org>.
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1000
@OutOfBedlam Thanks for the fix. LGTM. The failure of CI looks irrelevant.
---
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 if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---