You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by ch...@apache.org on 2012/10/22 17:20:28 UTC
[2/49] git commit: reducing line length to 80
reducing line length to 80
Project: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/commit/5aae00bc
Tree: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/tree/5aae00bc
Diff: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/diff/5aae00bc
Branch: refs/heads/4.0
Commit: 5aae00bc97b33aae879170e7d729da9436c56359
Parents: 6ec864a
Author: David Nalley <da...@gnsa.us>
Authored: Mon Oct 8 23:43:38 2012 -0400
Committer: Chip Childers <ch...@gmail.com>
Committed: Mon Oct 22 11:16:30 2012 -0400
----------------------------------------------------------------------
docs/en-US/volume-status.xml | 13 ++++++++++---
1 files changed, 10 insertions(+), 3 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/5aae00bc/docs/en-US/volume-status.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/volume-status.xml b/docs/en-US/volume-status.xml
index c2e58a5..35802f9 100644
--- a/docs/en-US/volume-status.xml
+++ b/docs/en-US/volume-status.xml
@@ -23,7 +23,14 @@
-->
<section id="volume-status">
- <title>Volume Status</title>
- <para>When a snapshot operation is triggered by means of a recurring snapshot policy, a snapshot is skipped if a volume has remained inactive since its last snapshot was taken. A volume is considered to be inactive if it is either detached or attached to a VM that is not running. &PRODUCT; ensures that at least one snapshot is taken since the volume last became inactive.</para>
- <para>When a snapshot is taken manually, a snapshot is always created regardless of whether a volume has been active or not.</para>
+ <title>Volume Status</title>
+ <para>When a snapshot operation is triggered by means of a recurring snapshot
+ policy, a snapshot is skipped if a volume has remained inactive since its
+ last snapshot was taken. A volume is considered to be inactive if it is
+ either detached or attached to a VM that is not running. &PRODUCT; ensures
+ that at least one snapshot is taken since the volume last became inactive.
+ </para>
+ <para>When a snapshot is taken manually, a snapshot is always created
+ regardless of whether a volume has been active or not.
+ </para>
</section>