[GitHub] zeppelin pull request #2408: [DOC][HOTFIX] Fix latest version typo

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] zeppelin pull request #2408: [DOC][HOTFIX] Fix latest version typo

zjffdu
GitHub user minahlee opened a pull request:

    https://github.com/apache/zeppelin/pull/2408

    [DOC][HOTFIX] Fix latest version typo

    ### What is this PR for?
    Fix version typo in nav menu from 0.7.1 to 0.7.2
   
    ### What type of PR is it?
    Documentation | Hot Fix
   
    ### Todos
    * [ ] - Task
   
    ### Questions:
    * Does the licenses files need update? no
    * Is there breaking changes for older versions? no
    * Does this needs documentation? no


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/minahlee/zeppelin fix/navMenu

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/2408.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 #2408
   
----
commit b6eef77b46ff95ed82e3f5bd562aed3d1dbd6a92
Author: Mina Lee <[hidden email]>
Date:   2017-06-13T16:51:49Z

    Fix latest version 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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] zeppelin pull request #2408: [DOC][HOTFIX] Fix latest version typo

zjffdu
Github user asfgit closed the pull request at:

    https://github.com/apache/zeppelin/pull/2408


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---