Author: tomaz
Date: Sat Sep 10 20:03:20 2011
New Revision: 795561

Log:
Publishing merge to libcloud site by tomaz

Modified:
    websites/production/libcloud/   (props changed)
    websites/production/libcloud/content/contributing.html
    websites/production/libcloud/content/css/libcloud.css

Propchange: websites/production/libcloud/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Sat Sep 10 20:03:20 2011
@@ -1 +1 @@
-/websites/staging/libcloud/trunk:787380-795553
+/websites/staging/libcloud/trunk:787380-795560

Modified: websites/production/libcloud/content/contributing.html
==============================================================================
--- websites/production/libcloud/content/contributing.html (original)
+++ websites/production/libcloud/content/contributing.html Sat Sep 10 20:03:20 
2011
@@ -83,17 +83,17 @@
 <li>Start a discussion on the <a href="devinfo.html">mailing list</a> (this 
step is optional and only required if you want to implement big feature or a 
change)</li>
 <li>Open a new issue on the <a 
href="https://issues.apache.org/jira/browse/LIBCLOUD";>bug tracker</a> 
(Jira)</li>
 <li>Fork libcloud <a href="https://github.com/apache/libcloud";>github git 
repository</a>* and make your changes</li>
-<li>Create a new branch for your changes (e.g. git checkout -b 
jira_issue_id_change_name)</li>
+<li>Create a new branch for your changes:<code>git checkout -b 
jira_issue_id_change_name</code></li>
 <li>Make your changes</li>
-<li>Write tests for your modifications and make sure that all the tests still 
pass (python setup.py test)</li>
+<li>Write tests for your modifications and make sure that all the tests still 
pass. For more informations about running the tests refer to the <a 
href="/testing.html">Testing</a> page.</li>
 <li>Create a patch with your changes</li>
-<li>git (format-patch): git format-patch --stdout trunk &gt; 
patch_name.patch</li>
-<li>git (diff): git diff --no-prefix trunk your_branch &gt; 
patch_name.patch</li>
-<li>svn: svn diff &gt; patch_name.patch</li>
+<li>git (format-patch): <code>git format-patch --stdout trunk &gt; 
patch_name.patch</code></li>
+<li>git (diff): <code>git diff --no-prefix trunk your_branch &gt; 
patch_name.patch</code></li>
+<li>svn: <code>svn diff &gt; patch_name.patch</code></li>
 <li>Attach patch to the ticket you have created</li>
 <li>Wait for your patch to be reviewed and / or accepted</li>
 </ol>
-<p><em>Note: If you want you can also use SVN repository, bit git and github 
make branching and contributing a bit easier.</em></p>
+<p><em>Note: If you want you can also use SVN repository, but git and github 
make branching and contributing a bit easier.</em></p>
       
     </div>
 

Modified: websites/production/libcloud/content/css/libcloud.css
==============================================================================
--- websites/production/libcloud/content/css/libcloud.css (original)
+++ websites/production/libcloud/content/css/libcloud.css Sat Sep 10 20:03:20 
2011
@@ -37,7 +37,7 @@ h2 { color:#007bff;}
 
 div#main { font-size: 120%; }
 
-pre, code { font-family:"Consolas", "Courier New", "Courier", "Lucida 
Console", fixed-width; padding:10px; background:#f5f5f5; border:1px solid #ddd; 
display:block; white-space:pre; color: #000000}
+pre, code { font-family:"Consolas", "Courier New", "Courier", "Lucida 
Console", fixed-width; padding:10px; margin: 3px;background:#f5f5f5; border:1px 
solid #ddd; display:block; white-space:pre; color: #000000}
 
 .support-table td, #support-table th { width:14%; border-right:1px solid #fff; 
border-bottom:1px solid #ddd;}
 .support-table th { background:#f5f5f5; }


Reply via email to