You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@edgent.apache.org by dlaboss <gi...@git.apache.org> on 2017/01/16 21:31:38 UTC

[GitHub] incubator-edgent pull request #275: [Edgent-366] Tolerate trailing spaces in...

GitHub user dlaboss opened a pull request:

    https://github.com/apache/incubator-edgent/pull/275

    [Edgent-366] Tolerate trailing spaces in serverURLs MqttConfig properties file

    Had a space at the end of the property and it was unclear why the URL
    failed validation.

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

    $ git pull https://github.com/dlaboss/incubator-edgent mqttConfig

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

    https://github.com/apache/incubator-edgent/pull/275.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 #275
    
----
commit 9c08a34e223f9d0c951b6f7ccc1e977c899a14f9
Author: Dale LaBossiere <dl...@us.ibm.com>
Date:   2017-01-16T20:54:53Z

    Tolerate trailing spaces in serverURLs MqttConfig properties file
    
    Had a space at the end of the property and it was unclear why the URL
    failed validation.

----


---
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] incubator-edgent pull request #275: [Edgent-366] Tolerate trailing spaces in...

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

    https://github.com/apache/incubator-edgent/pull/275


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