x/ranger
Code Issues Proposed changes

Update and replace http with https for doc links in ranger

Browse Source 
1) Update doc links according to OpenStack document migration
2) Use https instead of http for docs links

Change-Id: I2b90bf308c55264e2aa7e2035611f49db179fa60
This commit is contained in:
shangxiaobj 2017-08-15 19:09:21 -07:00
parent eb87b2bff6
commit a622e99e93
8 changed files with 11 additions and 11 deletions

4
orm/common/client/audit/CONTRIBUTING.rst

@ -1,14 +1,14 @@
If you would like to contribute to the development of OpenStack, you must
follow the steps in this page:
http://docs.openstack.org/infra/manual/developers.html
https://docs.openstack.org/infra/manual/developers.html
If you already have a good understanding of how the system works and your
OpenStack accounts are set up, you can skip to the development workflow
section of this documentation to learn how changes to OpenStack should be
submitted for review via the Gerrit tool:
http://docs.openstack.org/infra/manual/developers.html#development-workflow
https://docs.openstack.org/infra/manual/developers.html#development-workflow
Pull requests submitted through GitHub will be ignored.

2
orm/common/client/audit/HACKING.rst

@ -1,4 +1,4 @@
audit_client Style Commandments
===============================================
Read the OpenStack Style Commandments http://docs.openstack.org/developer/hacking/
Read the OpenStack Style Commandments https://docs.openstack.org/hacking/latest/

2
orm/common/client/audit/setup.cfg

@ -5,7 +5,7 @@ description-file =
README.rst
author = OpenStack
author-email = openstack-dev@lists.openstack.org
home-page = http://www.openstack.org/
home-page = https://www.openstack.org/
classifier =
Environment :: OpenStack
Intended Audience :: Information Technology

4
orm/common/client/keystone/CONTRIBUTING.rst

@ -1,14 +1,14 @@
If you would like to contribute to the development of OpenStack, you must
follow the steps in this page:
http://docs.openstack.org/infra/manual/developers.html
https://docs.openstack.org/infra/manual/developers.html
If you already have a good understanding of how the system works and your
OpenStack accounts are set up, you can skip to the development workflow
section of this documentation to learn how changes to OpenStack should be
submitted for review via the Gerrit tool:
http://docs.openstack.org/infra/manual/developers.html#development-workflow
https://docs.openstack.org/infra/manual/developers.html#development-workflow
Pull requests submitted through GitHub will be ignored.

2
orm/common/client/keystone/HACKING.rst

@ -1,4 +1,4 @@
keystone_utils Style Commandments
===============================================
Read the OpenStack Style Commandments http://docs.openstack.org/developer/hacking/
Read the OpenStack Style Commandments https://docs.openstack.org/hacking/latest/

2
orm/common/client/keystone/setup.cfg

@ -5,7 +5,7 @@ description-file =
README.rst
author = OpenStack
author-email = openstack-dev@lists.openstack.org
home-page = http://www.openstack.org/
home-page = https://www.openstack.org/
classifier =
Environment :: OpenStack
Intended Audience :: Information Technology

4
orm/services/region_manager/readme.md

@ -15,7 +15,7 @@ _TBD_
## Code style guide
First of all please read two of the following documents:
1. [Pythons PEP8](https://www.python.org/dev/peps/pep-0008/)
1. [Openstack hacking](http://docs.openstack.org/developer/hacking/)
1. [Openstack hacking](https://docs.openstack.org/hacking/latest/)
__After reading this please read it 3 more times__
@ -32,4 +32,4 @@ BusinessLogic
```
## Python tips and tricks
# test header
# test header

2
setup.cfg

@ -6,7 +6,7 @@ description-file =
README.rst
author = OpenStack
author-email = openstack-dev@lists.openstack.org
home-page = http://www.openstack.org/
home-page = https://www.openstack.org/
classifier =
Environment :: OpenStack
Intended Audience :: Information Technology