From 25357ca17914dbae2732241245d05f0af91db264 Mon Sep 17 00:00:00 2001
From: Francis Rowe <info@gluglug.org.uk>
Date: Wed, 18 Nov 2015 02:43:05 -0500
Subject: git page: make more clear how to submit patches

---
diff --git a/site/git/index.php b/site/git/index.php
index f4b50ed..0c91e2b 100644
--- a/site/git/index.php
+++ b/site/git/index.php
@@ -49,6 +49,7 @@
 					<li><a href="#guidelines">General guidelines for submitting patches</a></li>
 					<li><a href="#download">How to download</a></li>
 					<li><a href="#contrib">How to use git, for creating patches</a></li>
+					<li><a href="#sendpatch">How to send your patches</a></li>
 					<li><a href="#gitbackup">Backup git repositories</a></li>
 				</ul>
 
@@ -207,6 +208,14 @@
 						$ <strong>git lol</strong><br/>
 						<?php echo gettext("This is like <strong>git log</strong>, but it's much better and shows branches, etc."); ?>
 					</p>
+
+			<p>
+				<a href="#pagetop">Back to top of page</a>
+			</p>
+	</div>
+
+	<div>
+		<h1 id="sendpatch">How to submit your patches</h1>
 					<h3><?php echo gettext("Method 1: host a repository"); ?></h3>
 						<p>
 							<?php echo gettext("Give the checkout details to the libreboot project, along with information on which commits in what branch contain your changes."); ?>
@@ -224,10 +233,6 @@
 					<p>
 						<?php echo gettext("Contact the libreboot project using the details on the home page, sending your patch(es). The mailing list is generally preferable, although IRC can also be just as good for small patches (you would probably put the patch on a paste site). If you'll be using the mailing list(s) a lot, then it probably makes sense to subscribe to them."); ?>
 					</p>
-
-			<p>
-				<a href="#pagetop">Back to top of page</a>
-			</p>
 	</div>
 
 	<div>
--
cgit v0.9.1