r833 - trunk/patches

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Wed Aug 18 06:02:41 PDT 2004


Author: jeroen
Date: 2004-08-18 07:02:40 -0600 (Wed, 18 Aug 2004)
New Revision: 833

Modified:
   trunk/patches/submit.html
Log:
Adjust patches requirements according to Tushars instructions

Modified: trunk/patches/submit.html
===================================================================
--- trunk/patches/submit.html	2004-08-18 12:35:49 UTC (rev 832)
+++ trunk/patches/submit.html	2004-08-18 13:02:40 UTC (rev 833)
@@ -83,7 +83,9 @@
 			<dt>Initial Package Version</dt>
 				<dd>Version against which the patch was initially prepared.</dd>
 			<dt>Upstream Status</dt>
-				<dd>Wether the patch has been submitted to and/or accepted by the original developers. Mandatory.</dd>
+				<dd>Whether the patch has been submitted to and/or accepted by the original developers. The following are some suggestions for this field along with the explanations:
				<dl>
+					<dt>Not submitted - LFS Specific</dt>
					<dd>The patch is specific to LFS and has no value upstream. This should generally be avoided.</dd>
					<dt>Not submitted - [Test Version, Hack, Maintainer AWOL, ...]</dt>
					<dd>The patch has not been submitted upstream for some reason - e.g. the patch needs to be properly tested, the patch is a hack that will not be acceptable upstream, the maintainer is AWOL, ...</dd>
					<dt>From Upstream</dt>
					<dd>The patch is submitted upstream (not necessarily by you) and will be available in a future release.</dd>
					<dt>Submitted Upstream</dt>
					<dd>The patch has been submitted upstream (not necessarily by you) but there is no word yet from the maintainers.</dd>
					<dt>Rejected Upstream</dt>
					<dd>The patch was submitted upstream (not necessarily by you) but was rejected by the maintainers.</dd>
+      			</dl>
				If someone other than you had submitted the patch upstream, please acknowledge the person in the Description section. Also, it is always useful to add an URI for the relevant discussion.</dd>
 			<dt>Origin</dt>
 				<dd>Where the patch originated. This is useful for the users when considering whether to apply the patch. Please keep this field short and restricted to a single line. A URI to a mailing-list discussion on the patch is the best fit for this field. Another option, if the patch is taken from a distro package is to write the name of the distribution and the package name (e.g. Redhat mozilla-1.4-12.src.rpm). If the patch is created by you and there is no URI to reference, just add your name in the field.</dd>
 			<dt>Description</dt>




More information about the website mailing list