# HG changeset patch
# User Arne Babenhauserheide <bab@draketo.de>
# Date 1240562796 -7200
# Node ID f3bf81b67f7b3e79debccb0a14d2be8a3155a70f
# Parent  7666e300f28450595ed0ee7fbfcb8209c7cfc7c1
workflows: Added the basic patch submission workflow.

diff -r 7666e300f284 -r f3bf81b67f7b text/workflows.txt
--- a/text/workflows.txt	Fri Apr 24 10:33:29 2009 +0200
+++ b/text/workflows.txt	Fri Apr 24 10:46:36 2009 +0200
@@ -37,14 +37,36 @@
 
 === One-off patch submission ===
 
-==== Use Case ==== 
+==== For whom? ==== 
+
+If you just want to submit a short patch to a project, this workflow is right for you. 
 
 ==== Requirements ====
 
+You need just Mercurial (command line) and an email address to which you can send the patch. 
+
 ==== Flow ====
 
-- local work
-- sharing changes
+First get the repository
+
+$ hg clone http://hg-scm.org/hello
+
+Now do and commit your changes
+
+$ cd hello
+$ (edit files)
+$ hg add (new files)
+$ hg commit -m 'short descriptioni of the changes'
+
+Export your patch
+
+$ hg export tip &gt; patch.diff
+
+And send patch.diff to the developers email address, ideally with a description what your patch does and why it's important. 
+
+==== Modifications ====
+
+You can also upload the patch, for example to a bugtracker. 
 
 == Lone Developer ==