You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by hanm <gi...@git.apache.org> on 2017/03/21 19:05:09 UTC

[GitHub] zookeeper pull request #202: ZOOKEEPER-2635: regenerate document for branch-...

GitHub user hanm opened a pull request:

    https://github.com/apache/zookeeper/pull/202

    ZOOKEEPER-2635: regenerate document for branch-3.5 before release.

    Will create a separate PR for master (though there is not much need, but previous commit by Flavio also updated doc for master, so just for completeness sake.).
    
    I don't believe anyone is going to review bin diffs by naked eye, so I am going to merge this right away.

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

    $ git pull https://github.com/hanm/zookeeper ZOOKEEPER-2635

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

    https://github.com/apache/zookeeper/pull/202.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 #202
    
----
commit e91834f25187c6cc175021038691df1a49160d5e
Author: Michael Han <ha...@apache.org>
Date:   2017-03-21T19:03:09Z

    ZOOKEEPER-2635: regenerate document for branch-3.5 before release.

----


---
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] zookeeper pull request #202: ZOOKEEPER-2635: regenerate document for branch-...

Posted by hanm <gi...@git.apache.org>.
Github user hanm closed the pull request at:

    https://github.com/apache/zookeeper/pull/202


---
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.
---