diff options
author | Adam J. Stewart <ajstewart426@gmail.com> | 2016-08-24 10:42:23 -0500 |
---|---|---|
committer | Adam J. Stewart <ajstewart426@gmail.com> | 2016-08-30 15:29:51 -0500 |
commit | 02239c094e6634912ad75e416a12794154449b01 (patch) | |
tree | 5c81133a1e2e70a1ad2f0ea7911ef6c9014701c0 /lib | |
parent | eb56744f4d4fbbccb25dbd2042a9b28397bcca81 (diff) | |
download | spack-02239c094e6634912ad75e416a12794154449b01.tar.gz spack-02239c094e6634912ad75e416a12794154449b01.tar.bz2 spack-02239c094e6634912ad75e416a12794154449b01.tar.xz spack-02239c094e6634912ad75e416a12794154449b01.zip |
Fix unexpected indentation in .rst files, #1612
Diffstat (limited to 'lib')
-rw-r--r-- | lib/spack/docs/basic_usage.rst | 2 | ||||
-rw-r--r-- | lib/spack/docs/packaging_guide.rst | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/lib/spack/docs/basic_usage.rst b/lib/spack/docs/basic_usage.rst index ef01f616cd..a3cec2cc8b 100644 --- a/lib/spack/docs/basic_usage.rst +++ b/lib/spack/docs/basic_usage.rst @@ -1793,7 +1793,7 @@ Spack currently needs to be run from a filesystem that supports ``flock`` locking semantics. Nearly all local filesystems and recent versions of NFS support this, but parallel filesystems may be mounted 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: .. code-block:: sh diff --git a/lib/spack/docs/packaging_guide.rst b/lib/spack/docs/packaging_guide.rst index c6ac6dd7ef..0c0554c24a 100644 --- a/lib/spack/docs/packaging_guide.rst +++ b/lib/spack/docs/packaging_guide.rst @@ -607,7 +607,7 @@ always simple, though, so this is not strictly enforced. When fetching from from the branch corresponding to the development version (often called ``master``,``trunk`` or ``dev``), it is recommended to 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 greater than any other version. The rationale is that certain features or options first appear in the development branch. Therefore if a package author |