[GitHub] incubator-flink pull request: quick and dirty fix for FLINK-927 an...

[zentol]

GitHub user rwaury opened a pull request:

    https://github.com/apache/incubator-flink/pull/11

    quick and dirty fix for FLINK-927 and added more diagnostics information

   

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

    $ git pull https://github.com/rwaury/incubator-flink flink927

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

    https://github.com/apache/incubator-flink/pull/11.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 #11
   
----
commit 1e980dd89b064f2da039dd8ef0af9d7470108a19
Author: rwaury <[hidden email]>
Date:   2014-06-12T14:18:59Z

    quick and dirty fix for FLINK-927 and added more diagnostics information

----


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

[zentol]

Github user rmetzger commented on the pull request:

    https://github.com/apache/incubator-flink/pull/11#issuecomment-45949335
 
    Merged into master and 0.5.1.
   
    Please close the pull request (only the author of the PR can close it)


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

[zentol]

Github user rwaury closed the pull request at:

    https://github.com/apache/incubator-flink/pull/11


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