From 0481f6bbc88d089dea9b4979d10d2c957bfa4451 Mon Sep 17 00:00:00 2001
From: Francis Rowe <info@gluglug.org.uk>
Date: Wed, 18 Nov 2015 02:53:34 -0500
Subject: git page: move patch sending instructions to near top of page

---
(limited to 'site/git')

diff --git a/site/git/index.php b/site/git/index.php
index 0930bed..04fa6ae 100644
--- a/site/git/index.php
+++ b/site/git/index.php
@@ -133,6 +133,27 @@
 	</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."); ?>
+						</p>
+						<p>
+							You can email this information to <a href="mailto:<?php echo $devMailingListEmail; ?>"><?php echo $devMailingListEmail; ?></a>, which is the mailing list used for libreboot development discussion.
+						</p>
+					<h3><?php echo gettext("Method 2: git format-patch -N"); ?></h3>
+						<p>
+							<?php echo gettext("Use this method (replace N with the number of commits that you made) and send the .patch files to the libreboot project, along with details on what branch and revision these were made on top of."); ?>
+						</p>
+						<p>
+							You can email your patches to <a href="mailto:<?php echo $devMailingListEmail; ?>"><?php echo $devMailingListEmail; ?></a>, which is the mailing list used for libreboot development discussion.
+						</p>
+					<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>
+	</div>
+
+	<div>
 				<h2 id="contrib"><?php echo gettext("How to use git, for creating patches"); ?>  <span class="r"><a href="#contrib">#contrib</a></span></h2>
 					<p>
 						Libreboot development is facilitated by <em>git</em>, a <em>distributed</em> version control system that is in wide use today. Git provides many practical benefits,
@@ -215,27 +236,6 @@
 	</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."); ?>
-						</p>
-						<p>
-							You can email this information to <a href="mailto:<?php echo $devMailingListEmail; ?>"><?php echo $devMailingListEmail; ?></a>, which is the mailing list used for libreboot development discussion.
-						</p>
-					<h3><?php echo gettext("Method 2: git format-patch -N"); ?></h3>
-						<p>
-							<?php echo gettext("Use this method (replace N with the number of commits that you made) and send the .patch files to the libreboot project, along with details on what branch and revision these were made on top of."); ?>
-						</p>
-						<p>
-							You can email your patches to <a href="mailto:<?php echo $devMailingListEmail; ?>"><?php echo $devMailingListEmail; ?></a>, which is the mailing list used for libreboot development discussion.
-						</p>
-					<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>
-	</div>
-
-	<div>
 				<h2 id="gitbackup"><?php echo gettext("Backup repositories"); ?>  <span class="r"><a href="#gitbackup">#gitbackup</a></span></h2>
 
 					<h3><?php echo gettext("Firmware (coreboot distribution)"); ?></h3>
--
cgit v0.9.1