cvs commit: www/test/patches index.html

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Tue Aug 19 08:10:23 PDT 2003


jeroen      03/08/19 09:10:23

  Modified:    test/hints list.html
               test/patches index.html
  Log:
  Update the hints list to include Bill's boot_any_hd.txt hint. Some small spell fixes and rewording to the patch page.
  
  Revision  Changes    Path
  1.22      +2 -3      www/test/hints/list.html
  
  Index: list.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/hints/list.html,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- list.html	19 Aug 2003 02:29:23 -0000	1.21
  +++ list.html	19 Aug 2003 15:10:23 -0000	1.22
  @@ -43,8 +43,6 @@
   
   <h2>Hints Index</h2>
   
  -<p><strong>Warning: temporarily out of date!</strong></p>
  -
   <div id="pagenav">
   	<ul>
   		<li><a href="#booting">Booting</a></li>
  @@ -65,7 +63,8 @@
   <h3 id="booting">Booting</h3>
   	<ul>
   		<li><a href="files/bootcd.txt">Boot-CD</a><br />How to create a bootcd from a working LFS system.</li>
  -		<li><a href="files/boot_any_hd_sample_apps.txt">Boot (not just root) any HD, sample application.</a><br /> Examples of practical application of the boot_any_hd.txt hint.</li>
  +		<li><a href="files/boot_any_hd.txt">Boot (not just root) any HD.</a><br /><strong>Boot</strong> any OS from any hard drive, with recent BIOS and Lilo.</li>
  +		<li><a href="files/boot_any_hd_sample_apps.txt">Boot (not just root) any HD, sample application.</a><br />Examples of practical application of the boot_any_hd.txt hint.</li>
   		<li><a href="files/bootlfscd.txt">Bootable LFS CD using lilo</a><br />This hint involves using two LFS systems to build a third system on a CD. It does not use any external packages, the boot method being LFS.</li>
   		<li><a href="files/boot-cd_easy.txt">Easy Boot CD of your LFS</a><br />How to create an easy Boot CD of your working LFS system.</li>
   		<li><a href="files/grub_boot_rescue.txt">GRUB Boot & Rescue Disk - HOWTO</a><br />GRUB is the GRand Unified Bootloader, a boot loader program with many cool features for the PC. It serves as a replacement for the more traditional LILO. This hint shows how to use GRUB to make a combined boot loader and rescue disk for your LFS system.</li>
  
  
  
  1.2       +5 -5      www/test/patches/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/patches/index.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- index.html	19 Aug 2003 13:05:16 -0000	1.1
  +++ index.html	19 Aug 2003 15:10:23 -0000	1.2
  @@ -55,7 +55,7 @@
   </div>
   
   	<h3 id="info">General information</h3>
  -		<p>The <a href="mailto:patches at linuxfromscratch.org">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>
  +		<p>The <a href="mailto:patches at linuxfromscratch.org">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 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>
  @@ -82,7 +82,7 @@
   				</dl>
   			</li>
   			<li>
  -				<p>The patch should have the following information each on a seperate line:</p>
  +				<p>The patch should have the following information, each item on a seperate line:</p>
   				<dl>
   					<dt>Submitted By</dt>
   						<dd>Name and/or E-mail of submitter.</dd>
  @@ -91,13 +91,13 @@
   					<dt>Initial Package Version</dt>
   						<dd>Version against which the patch was initially prepared.</dd>
   					<dt>Origin</dt>
  -						<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>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>
   					<dt>Description</dt>
   						<dd>Description of what the patch does, links to discussion(s) related to the patch, etc.</dd>
   				</dl>
   				<p><em>Note: See the <a href="package-1.0-sample4patch.patch">sample patch</a>.</em></p>
   			</li>
  -			<li><p>Patches should be mailed to <a href="mailto:patches at linuxfromscratch.org">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>Patches should be mailed to <a href="mailto:patches at linuxfromscratch.org">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 submission 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="http://linuxfromscratch.org/mailman/listinfo/patches">the mailing list information page</a> for details on the mailing list.</p></li>
   		</ul>
   
  @@ -111,7 +111,7 @@
   		</ul>
   
   	<h3 id="todo">Todo</h3>
  -		<p>Create a script which creates a table like this:</p>
  +		<p>Create a script which creates a table from the patches index. Extract some usefull information, like patch submitter, origin, description/purpose and of course the diff itself.</p>
   	<table>
   	<tbody>	
   		<tr>
  
  
  



More information about the website mailing list