Fix unexpected indentation in .rst files, #1612

This commit is contained in:
Adam J. Stewart 2016-08-24 10:42:23 -05:00
parent eb56744f4d
commit 02239c094e
2 changed files with 2 additions and 2 deletions

View File

@ -1793,7 +1793,7 @@ Spack currently needs to be run from a filesystem that supports
``flock`` locking semantics. Nearly all local filesystems and recent ``flock`` locking semantics. Nearly all local filesystems and recent
versions of NFS support this, but parallel filesystems may be mounted versions of NFS support this, but parallel filesystems may be mounted
without ``flock`` support enabled. You can determine how your without ``flock`` support enabled. You can determine how your
filesystems are mounted with ``mount -p``. The output for a Lustre filesystems are mounted with ``mount -p``. The output for a Lustre
filesystem might look like this: filesystem might look like this:
.. code-block:: sh .. code-block:: sh

View File

@ -607,7 +607,7 @@ always simple, though, so this is not strictly enforced.
When fetching from from the branch corresponding to the development version When fetching from from the branch corresponding to the development version
(often called ``master``,``trunk`` or ``dev``), it is recommended to (often called ``master``,``trunk`` or ``dev``), it is recommended to
call this version ``develop``. Spack has special treatment for this version so call this version ``develop``. Spack has special treatment for this version so
that ``@develop`` will satisfy dependencies like that ``@develop`` will satisfy dependencies like
``depends_on(abc, when="@x.y.z:")``. In other words, ``@develop`` is ``depends_on(abc, when="@x.y.z:")``. In other words, ``@develop`` is
greater than any other version. The rationale is that certain features or greater than any other version. The rationale is that certain features or
options first appear in the development branch. Therefore if a package author options first appear in the development branch. Therefore if a package author