Author: tomaz
Date: Sat Sep 10 19:53:00 2011
New Revision: 1167585

URL: http://svn.apache.org/viewvc?rev=1167585&view=rev
Log:
CMS commit to libcloud by tomaz

Modified:
    libcloud/site/trunk/content/contributing.mdtext

Modified: libcloud/site/trunk/content/contributing.mdtext
URL: 
http://svn.apache.org/viewvc/libcloud/site/trunk/content/contributing.mdtext?rev=1167585&r1=1167584&r2=1167585&view=diff
==============================================================================
--- libcloud/site/trunk/content/contributing.mdtext (original)
+++ libcloud/site/trunk/content/contributing.mdtext Sat Sep 10 19:53:00 2011
@@ -11,13 +11,13 @@ Keep in mind that all kind of contributi
  1. Start a discussion on the [mailing list](devinfo.html) (this step is 
optional and only required if you want to implement big feature or a change)
  1. Open a new issue on the [bug 
tracker](https://issues.apache.org/jira/browse/LIBCLOUD) (Jira)
  2. Fork libcloud [github git repository](https://github.com/apache/libcloud)* 
and make your changes
-   1. Create a new branch for your changes (e.g. git checkout -b 
jira_issue_id_change_name)
+   1. Create a new branch for your changes (e.g. `git checkout -b 
jira_issue_id_change_name`)
    2. Make your changes
-  3. Write tests for your modifications and make sure that all the tests still 
pass (python setup.py test)
+  3. Write tests for your modifications and make sure that all the tests still 
pass. For more informations about running the tests refer to the 
[/testing.html](Testing) page.
  3. Create a patch with your changes
-  1. git (format-patch): git format-patch --stdout trunk > patch_name.patch
-  2. git (diff): git diff --no-prefix trunk your_branch > patch_name.patch
-  3. svn: svn diff > patch_name.patch
+  1. git (format-patch): `git format-patch --stdout trunk > patch_name.patch`
+  2. git (diff): `git diff --no-prefix trunk your_branch > patch_name.patch`
+  3. svn: `svn diff > patch_name.patch`
  4. Attach patch to the ticket you have created
  5. Wait for your patch to be reviewed and / or accepted
 


Reply via email to