curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randgalt <...@git.apache.org>
Subject [GitHub] curator pull request #166: [CURATOR-345] clientAddr might be null in which c...
Date Wed, 28 Sep 2016 10:12:39 GMT
GitHub user Randgalt opened a pull request:

    https://github.com/apache/curator/pull/166

    [CURATOR-345] clientAddr might be null in which case addr should be used.

    

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

    $ git pull https://github.com/apache/curator CURATOR-345

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

    https://github.com/apache/curator/pull/166.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 #166
    
----
commit 1998491612c2b2658d776b6a71de41ac3d20e0f2
Author: randgalt <randgalt@apache.org>
Date:   2016-09-28T10:10:38Z

    clientAddr might be null in which case addr should be used.

----


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

Mime
View raw message