diff options
| author | Toshio Kuratomi <a.badger@gmail.com> | 2018-04-11 12:13:34 -0700 |
|---|---|---|
| committer | Toshio Kuratomi <a.badger@gmail.com> | 2018-04-11 13:26:15 -0700 |
| commit | 98a6827be07b8b1d49f9bcf56ed0bf9c6192ee23 (patch) | |
| tree | 073a74282b734a513583275e2c6a043859499365 /README.rst | |
| parent | 12431d23cdb47d89318b54575a5342418b26ba82 (diff) | |
| download | ansible-98a6827be07b8b1d49f9bcf56ed0bf9c6192ee23.tar.gz | |
When I rebased the README as rst PR, I missed a few changes.
Diffstat (limited to 'README.rst')
| -rw-r--r-- | README.rst | 10 |
1 files changed, 2 insertions, 8 deletions
diff --git a/README.rst b/README.rst index a7dae42616..c3fbc91da2 100644 --- a/README.rst +++ b/README.rst @@ -23,12 +23,6 @@ run directly from the development branch - while significant efforts are made to ``devel`` is reasonably stable, you're more likely to encounter breaking changes when running Ansible this way. -If you want to download a tarball of a release, go to -`releases.ansible.com <https://releases.ansible.com/ansible>`_, though -most users use ``yum`` (using the EPEL instructions linked above), -``apt`` (using the PPA instructions linked above), or -``pip install ansible``. - Design Principles ================= @@ -58,7 +52,7 @@ Get Involved ``git rebase`` vs ``git merge`` for this reason. If submitting a large code change (other than modules), it's probably a good idea to join ansible-devel and talk about what you would like to do or add - first and to avoid duplicate efforts. This not only helps everyone + first to avoid duplicate efforts. This not only helps everyone know what's going on, it also helps save time and effort if we decide some changes are needed. * Users list: @@ -91,7 +85,7 @@ Ansible was created by `Michael DeHaan <https://github.com/mpdehaan>`_ Ansible is sponsored by `Ansible, Inc <https://ansible.com>`_ -Licence +License ======= GNU General Public License v3.0 |