cvs commit: www/test/patches index.html

jeroen at jeroen at
Tue Aug 19 06:05:16 PDT 2003

jeroen      03/08/19 07:05:16

  Added:       test/patches index.html
  Bring in the patches. Nowhere near complete to being a good frontend for the patches, but it's a start.
  Revision  Changes    Path
  1.1                  www/test/patches/index.html
  Index: index.html
  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "">
  <html xmlns="" xml:lang="en">
  	<title>Patches - Linux From Scratch</title>
  	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
  	<meta http-equiv="Content-Style-Type" content="text/css" />
  	<meta name="description" content="Linux From Scratch - build your own Linux distribution from scratch" />
  	<meta name="keywords" content="Linux, LinuxFromScratch, Linux From Scratch, build your own Linux, DIY Linux, do-it-yourself Linux, create your own Linux" />
  	<meta http-equiv="imagetoolbar" content="false" />
  	<meta name="MSSmartTagsPreventParsing" content="true" />
  	<link rel="stylesheet" type="text/css" href="../style/screen.css" media="screen" />
  	<link rel="stylesheet" type="text/css" href="../style/print.css" media="print" />
  	<link rel="icon" href="images/favicon.ico" type="image/x-icon" />
  <body id="body" class="root">
  <div id="header">
  	<ul id="sectionnav">
  		<li><a href="#rootcontent" class="hidden" accesskey="2">Skip to content</a></li>
  		<li><a href="../lfs/news.html" accesskey="l"><span class="accesskey">L</span>FS</a></li>
  		<li><a href="../blfs/news.html" accesskey="b"><span class="accesskey">B</span>eyond LFS</a></li>
  		<li><a href="../alfs/news.html" accesskey="a"><span class="accesskey">A</span>utomated LFS</a></li>
  		<li><a href="../hints/news.html" accesskey="h"><span class="accesskey">H</span>ints</a></li>
  	<h1><a href="../lfs/news.html" accesskey="l">Linux From Scratch</a></h1><span class="hidden"> - </span>
  	<h2><a href="../lfs/whatislfs.html">Your distro. Your rules.</a></h2>
  	<div id="search">
  		<form method="get" action="">
  			<label title="Enter your search terms"><input size="15" type="text" name="query" onfocus="if(this.value==this.defaultValue) this.value='';" value="enter text here" maxlength="255" accesskey="s" /></label>
  			<label title="Submit the search terms"><input type="submit" value="search" /></label><br />
  			<a href="../search.html" title="For more search options, click here" accesskey="4"><span class="accesskey">S</span>earch options</a>
  <div id="container">
  <div id="rootcontent">
  	<em><a href="#generalnav" class="hidden">Skip to sitewide navigation</a></em>
  <div id="pagenav">
  		<li><a href="#info">General information</a></li>
  		<li><a href="#about">About patches</a></li>
  		<li><a href="#submit">Submit patches</a></li>
  		<li><a href="">Browse the patches</a></li>
  			<!-- This link should point to a section on this page, which will give readers the choice to browse the patches like FTP or via a table -->
  		<li><a href="#todo">Todo</a></li>
  		<li><a href="#changelog">Changelog</a></li>
  	<h3 id="info">General information</h3>
  		<p>The <a href="mailto:patches at">patches mailinglist</a> is for submission of non-critical patches for various packages for LFS and BLFS. This list is only for <em>submission</em> of patches, discussion related to patches should be on the appropriate support or development list; mostly this would be either blfs-dev or lfs-dev. This list shouldn't lead to fragmetation of discussions, so please be sure to send your patches to the discussion list and CC the patches list.</p>
  	<h3 id="about">About the patches</h3>
  		<p>This should state what patches we're interested in and which ones we're not.</p>
  	<h3 id="submit">Patches Submission Guidelines:</h3>
  				<p>The patch should be created with the following command for consistency:</p>
  				<p><code>LC_ALL=C TZ=UTC0 diff -Naur [old...] [new...] > [patch name...].patch</code></p>
  				<p>When creating the patch, you should be in a directory just above the package directory so that the resulting patch can be applied with <code>patch -p1</code> as per the current instrunctions in the book.</p>
  				<p>The patch file name should be in the following format:</p>
  						<dd>Official name of the package.</dd>
  						<dd>Version against which the patch applies.</dd>
  						<dd>Short name for the patch (also include architecture if the patch is for a particular architecture.</dd>
  						<dd>Version of the patch (usually 1). This field is optional.</dd>
  				<p>The patch should have the following information each on a seperate line:</p>
  					<dt>Submitted By</dt>
  						<dd>Name and/or E-mail of submitter.</dd>
  						<dd>Date Patch Submitted in YYYY-MM-DD format. It is easier for everyone to comprehend the international format, please do not use any other.</dd>
  					<dt>Initial Package Version</dt>
  						<dd>Version against which the patch was initially prepared.</dd>
  						<dd>Where the patch originated. This is useful for the users when considering whether to apply the patch. If you made the patch, put your name. the more information you give to potential appliers of the patch, the better chance it has of being used.</dd>
  						<dd>Description of what the patch does, links to discussion(s) related to the patch, etc.</dd>
  				<p><em>Note: See the <a href="package-1.0-sample4patch.patch">sample patch</a>.</em></p>
  			<li><p>Patches should be mailed to <a href="mailto:patches at">the patches mailing list</a>. I prefer receiving URLs also along with the patches so that I can download the patches using wget instead of saving attachments. Even if you include a URL, please attach the patch along with your subission for archives. Please gzip or bzip2 the patches so that it is easy for people to download the patches directly from the list archives. At the same time it saves some bandwidth. I will gunzip or bunzip2 the patches before posting so that they can be viewed online.</p></li>
  			<li><p>Refer to <a href="">the mailing list information page</a> for details on the mailing list.</p></li>
  	<h3 id="browse">Browse patches</h3>
  		<p>You can view the patches in a couple of ways:</p>
  			<li><a href="#">Sorted by package</a></li>
  			<li><a href="#">Sorted by submitter</a></li>
  			<li><a href="#">Sorted by date</a></li>
  			<li><a href="#">Unsorted</a></li>
  	<h3 id="todo">Todo</h3>
  		<p>Create a script which creates a table like this:</p>
  			<th>Submitted By</th>
  			<td>Patches Project (<a href="mailto:patches at linuxfromscratch dot org">optional e-mail address</a>)</td>
  			<th>Initial Package Version</th>
  			<td>This is a sample patch. This was created so that there is an easy reference for those submitting patches.</td>
  	<pre>diff -Naur package-1.0.orig/README package-1.0/README
  	--- package-1.0.orig/README	2003-08-17 06:25:37.000000000 +0000
  	+++ package-1.0/README	2003-08-17 06:25:56.000000000 +0000
  	@@ -1,4 +1,3 @@
  	 Test file for patches project
  	-Who created this silly file.
  	 What is this new package package?
  	 Already at Version 1.0? Fast paced!!!</pre>
  	<p><strong>Actually, I'm not sure yet what the script should display in a table, and even if it should be a table.</strong></p>
  	<h3 id="changelog">Changelog</h3>
  		<p>Once the patches are brought into CVS, we can have a dynamically generated changelog like <a href="../lfs/news.html#changelog">LFS</a>, <a href="../blfs/news.html#changelog">BLFS</a>, <a href="../hints/news.html#changelog">the hints</a> and <a href="../website.html#changelog">the website</a>.</p>
  </div> <!-- end content -->
  <div id="generalnav">
  				<li><a href="../donation.html" title="We accept all donations, really">Make a donation</a></li>
  				<li><a href="" title="Register freely!">Register as LFS user</a></li>
  				<li><a href="../becomemirror.html" title="If you have some bandwidth to spare">Become a mirror</a></li>
  				<li><a href="../patches/" title="Submit patches for LFS or BLFS" class="currentpage">Submit patches</a></li>
  		<li><h3>Help and contact:</h3>
  				<li><a href="../faq/" title="Frequently Asked Questions (and answers!)">FAQ</a></li>
  				<li><a href="../search.html" title="Advanced search page">Search</a></li>
  				<li><a href="../irc.html" title="Yes we chat too">IRC</a></li>
  				<li><a href="../newsgroups.html" title="For following development and advanced support">News groups</a></li>
  				<li><a href="../mail.html" title="For following development and advanced support">Mailing lists</a></li>
  				<li><a href="../people.html" title="A list of user homepages hosted on LFS">People</a></li>
  		<li><h3>About this website:</h3>
  				<li><a href="../index.html" title="Home (mirror list)" accesskey="1">Home (Mirror list)</a></li>
  				<li><a href="../sitemap.html" title="Structured overview of the website" accesskey="3">Sitemap</a></li>
  				<li><a href="../accesskeys.html" title="Speed up your browsing" accesskey="0">Accesskeys</a></li>
  				<li><a href="../website.html" title="Todo, general information and changelog">Website information</a></li>
  				<li><a href="mailto:website at" title="Problems, questions or suggestions?" accesskey="9">Discuss this website</a></li>
  </div><!-- end generalnav -->
  </div><!-- end container -->
  <div id="footer">
  		<li><a href="#header">Back to the top.</a></li>
  		<li>© 1998-2003  Gerard Beekmans.</li>
  		<li>Site design by Jeroen Coumans.</li>
  		<li><a href=""><img src="../images/xhtml-1.1.png" alt="Valid XHTML 1.1!" height="15" width="80" /></a></li>
  		<li><a href=""><img src="../images/css.png" alt="Valid CSS!" height="15" width="80" /></a></li>

More information about the website mailing list