# HG changeset patch
# User sheepluva
# Date 1452803950 0
# Node ID 67653ea060f22600f3a20d37d3a6ba29f62055ef
# Parent  92086cbfde4ca37ff166408bb0619b49918ddbae
Edited via web interface

diff -r 92086cbfde4c -r 67653ea060f2 ContributingCode.wiki
--- a/ContributingCode.wiki	Thu Jan 14 20:38:19 2016 +0000
+++ b/ContributingCode.wiki	Thu Jan 14 20:39:10 2016 +0000
@@ -14,25 +14,6 @@
 
 TODO
 
-=== Creating a (named) branch ===
-We prefer not to use (named) branches for little patches, as branches are permanent and will clutter the list of {{{hg branches}}}.
-So for small code contributions, use unnamed branches instead (see below).
-However, if you are going to write code that is more a pro#summary Useful hints for contributing code to Hedgewars
-
-
-*Table of Contents*
-<wiki:toc max_depth="2" />
-
-= Introduction =
-
-You want to contribute code to Hedgewars? That's great! Here are some hints how to help us with importing your code.
-
-= Recommended workflows =
-
-== Using a mercurial clone ==
-
-TODO
-
 === Using (named) branches ===
 Branches are alternative commit histories. Changes done in one branch can be merged into other branches as needed.