You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by raphtheb <gi...@git.apache.org> on 2014/08/15 20:23:32 UTC
[GitHub] libcloud pull request: [LIBCLOUD-544] Fix the regression caused by...
GitHub user raphtheb opened a pull request:
https://github.com/apache/libcloud/pull/348
[LIBCLOUD-544] Fix the regression caused by the original implementation ...
...of the bugfix. We now perform a simple sanity check to know whether the metadata dictionary has already been formatted to GCE's specs.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/raphtheb/libcloud LIBCLOUD-544_gce_metadata_fix
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/libcloud/pull/348.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 #348
----
commit 0efaf9d2ab2bb86ec286fadeb9a24e64d09416db
Author: rtheberge <ra...@bhvr.com>
Date: 2014-08-15T18:20:14Z
[LIBCLOUD-544] Fix the regression caused by the original implementation of the bugfix. We now perform a simple sanity check to know whether the metadata dictionary has already been formatted to GCE's specs.
----
---
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] libcloud pull request: [LIBCLOUD-544] Fix the regression caused by...
Posted by raphtheb <gi...@git.apache.org>.
Github user raphtheb closed the pull request at:
https://github.com/apache/libcloud/pull/348
---
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.
---