cvs commit: www/test/patches index-bottom.html index-top.html

jeroen at jeroen at
Tue Sep 2 00:07:25 PDT 2003

jeroen      03/09/02 01:07:25

  Added:       test/patches index-bottom.html index-top.html
  Import the templates for dynamic patch page.
  Revision  Changes    Path
  1.1                  www/test/patches/index-bottom.html
  Index: index-bottom.html
  </div> <!-- end content -->
  <div id="generalnav">
  				<li><a href="../donation.html" title="Donate via paypal">Make a donation</a></li>
  				<li><a href="" title="Get counted!">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="Chat channels and nick names">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="Who is who and who does what">The LFS team</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="Keyboard shortcuts for this site" accesskey="0">Accesskeys</a></li>
  				<li><a href="../website.html" title="General info about this site">Website information</a></li>
  				<li><a href="" title="Mail us if you run into problems with this website" accesskey="9">Contact webmaster</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>
  1.1                  www/test/patches/index-top.html
  Index: index-top.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="">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="#submit">Submit patches</a></li>
  		<li><a href="#todo">Todo</a></li>
  		<li><a href="#changelog">Changelog</a></li>
  	<h3 id="info">General information</h3>
  		<p>The patches project serves as a central repository for all patches useful for an LFS user. It also serves to be a testing ground for patches that may later be incorporated into the LFS and BLFS book. The patches that are not included in the book but are available from the patches repository are primarily meant for users already familiar with LFS. First time LFS users should adhere to the versions and patches which are in LFS or BLFS. </p>
  		<p>Patches are submitted by individual users, and may not be tested by the LFS Testing Team. They carry no warranty of any sort. Apply the patches at your own risk.</p>
  		<p>The <a href="" title="Archive and subscription information for the patches mailinglist">patches mailinglist</a> is only for <em>submission</em> of patches and for discussion related to the development of patches project. Discussion related to patches should be on the appropriate support or development list, mostly 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>
  		<p>The patches project is maintained by <a href="">Jim Gifford</a> and <a href="">Tushar Teredesai</a>.</p>
  	<h3 id="submit">Patches Submission Guidelines:</h3>
  				<p>Before submitting a patch, check if there is an already existing patch for the current version or a previous version. If there is a patch for the previous version that applies without an error (Note: Getting an offset/fuzz when applying the patch is not an error) just drop a note on the list and the patches mainitainers will copy the file over to the new version.</p>
  				<p>A suggested command for creating the patch file is:</p>
  				<p>LC_ALL=C TZ=UTC0 diff -Naur [old...] [new...] > [patch name...].patch</p>
  				<p>Note that this is not an absolute requirement and you are free to create the patch any way you like as long as the following requirement is satisfied.  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 item 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="" title="Archive and subscription information for the patches mailinglist">the patches mailing list</a>. The patches maintainers prefer receiving download URIs also along with the patches. Even if you include a URI, please attach the patch along with your submission for the 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. The patches will be gunziped or bunzip2ed before uploading 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><em class="highlight">This should be possible once we have an autogenerated table.</em></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>
  	<h3 id="todo">Todo</h3>
  		<p>Create a script which creates a table from the patches index. Extract some useful information, like download location, patch submitter, date, origin and the short description/purpose. New entries should preferably be added to the top. </p>
  			<th>Download location</th>
  			<th>Submitted By</th>
  			<td><a href="">package-1.0-sample4patch.patch</a></td>
  			<td><a href="mailto:#" title="e-mail adress">Patches Project</a></td>
  			<td><a href="">LFS patches website</a></td>
  			<td>This is a sample patch. This was created so that there is an easy reference for those submitting patches.</td>
  			<td><a href="">foo-1.0-anothersample2patch.patch</a></td>
  			<td><a href="mailto:#" title="e-mail adress">Patches Project</a></td>
  			<td><a href="">LFS patches website</a></td>
  			<td>Another sample patch. Just the same as the previous really.</td>
  			<td><a href="">bar-1.0-example4patch.patch</a></td>
  			<td><a href="mailto:#" title="e-mail adress">Patches Project</a></td>
  			<td><a href="">LFS patches website</a></td>
  			<td>Last sample patch. The structure of the table should be clear now. </td>
  	<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>The following changelog is automatically generated from CVS log messages and fed into this file. These changes are from last month.</p>

More information about the website mailing list