libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From raphtheb <...@git.apache.org>
Subject [GitHub] libcloud pull request: Libcloud 544 gce metadata fix
Date Fri, 15 Aug 2014 18:56:34 GMT
GitHub user raphtheb opened a pull request:

    https://github.com/apache/libcloud/pull/349

    Libcloud 544 gce metadata fix

    This is a slightly improved version of the fix i submitted minutes ago which had some
trace-generating code in it. Removed my own silly tests.

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/349.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 #349
    
----
commit 0efaf9d2ab2bb86ec286fadeb9a24e64d09416db
Author: rtheberge <raphael.theberge@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.

commit 29568b964578e449289128104786998e8866580a
Author: rtheberge <raphael.theberge@bhvr.com>
Date:   2014-08-15T18:51:31Z

    Remove my own tests before pushing, whoops.

----


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