GitHub user Mac21 opened a pull request:

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

    [LIBCLOUD-892] Improve GCE Compute driver docstrings.

    ## Changes Title (replace this with a logical title for your changes)
    
    ### Description
    
    Replace this with the PR description (mention the changes you have made, why
    you have made them, provide some background and any references to the 
provider
    documentation if needed, etc.).
    
    For more information on contributing, please see 
[Contributing](http://libcloud.readthedocs.org/en/latest/development.html#contributing)
    section of our documentation.
    
    ### Status
    
    Replace this: describe the PR status. Examples:
    
    - work in progress
    - done, ready for review
    
    ### Checklist (tick everything that applies)
    
    - [ ] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
    - [ ] Documentation
    - [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
    - [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


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

    $ git pull https://github.com/Mac21/libcloud gce_compute_driver_docfix

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

    https://github.com/apache/libcloud/pull/981.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 #981
    
----
commit 227912204585bd74bd5a8affa9ebbeb41b033086
Author: toller <[email protected]>
Date:   2017-02-02T17:16:21Z

    [LIBCLOUD-892] Improve GCE Compute driver docstrings.

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to