Author: buildbot
Date: Wed Dec 12 17:26:11 2012
New Revision: 841925

Log:
Staging update by buildbot for vcl

Modified:
    websites/staging/vcl/trunk/content/   (props changed)
    websites/staging/vcl/trunk/content/docs/changelog.html

Propchange: websites/staging/vcl/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Dec 12 17:26:11 2012
@@ -1 +1 @@
-1420851
+1420853

Modified: websites/staging/vcl/trunk/content/docs/changelog.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/changelog.html (original)
+++ websites/staging/vcl/trunk/content/docs/changelog.html Wed Dec 12 17:26:11 
2012
@@ -103,7 +103,7 @@
 <li>[<a href='https://issues.apache.org/jira/browse/VCL-632'>VCL-632</a>] -    
     vSphere_SDK.pm set_file_permissions does not work</li>
 <li>[<a href='https://issues.apache.org/jira/browse/VCL-633'>VCL-633</a>] -    
     Change of vmprofile.vmdisk value can cause image capture to fail due to 
insufficient space</li>
 <li>[<a href='https://issues.apache.org/jira/browse/VCL-634'>VCL-634</a>] -    
     Cluster reservations fail if node_status returns POST_LOAD</li>
-<li>[<a href='https://issues.apache.org/jira/browse/VCL-641'>VCL-641</a>] -    
     VCL fails to properly trim whitespace from <code>virsh list 
--all</code></li>
+<li>[<a href='https://issues.apache.org/jira/browse/VCL-641'>VCL-641</a>] -    
     VCL fails to properly trim whitespace from "virsh list --all"</li>
 <li>[<a href='https://issues.apache.org/jira/browse/VCL-642'>VCL-642</a>] -    
     colons should not be allowed in resource group names</li>
 <li>[<a href='https://issues.apache.org/jira/browse/VCL-643'>VCL-643</a>] -    
     VM Limit can be decreased to below the current number of assigned VMs</li>
 <li>[<a href='https://issues.apache.org/jira/browse/VCL-648'>VCL-648</a>] -    
     blockRequests re-processed at end time for skipped block time entries</li>


Reply via email to