cvs commit: www/hints submit.html

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Fri Sep 12 10:59:14 PDT 2003


jeroen      03/09/12 11:59:14

  Modified:    .        acknowledgements.html people.html
               hints    submit.html
  Log:
  Some minor textual corrections suggested by Tushar and Larry.
  
  Revision  Changes    Path
  1.7       +1 -1      www/acknowledgements.html
  
  Index: acknowledgements.html
  ===================================================================
  RCS file: /home/cvsroot/www/acknowledgements.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- acknowledgements.html	11 Sep 2003 20:13:59 -0000	1.6
  +++ acknowledgements.html	12 Sep 2003 17:59:14 -0000	1.7
  @@ -76,7 +76,7 @@
   		<li><a href="mailto:timothy@linuxfromscratch.org">Timothy Bauscher</a> for editing the LFS Book and maintaining the Hints project.</li>
   		<li><a href="mailto:ian@ichilton.co.uk">Ian Chilton</a> for maintaining the Hints project</li>
   		<li><a href="mailto:gimli@linuxfromscratch.org">Marc Heerdink</a> for editing the LFS Book.</li>
  -		<li><a href="mailto:markh@linuxfromscratch.org">Mark Hymers</a> for initiating and editing the LFS Book.</li>
  +		<li><a href="mailto:markh@linuxfromscratch.org">Mark Hymers</a> for initiating and editing BLFS and editing the LFS Book.</li>
   		<li><a href="mailto:sklein@linuxfromscratch.org">Seth W. Klein</a> for initiating and maintaining the LFS FAQ.</li>
   		<li><a href="mailto:garrett@linuxart.com">Garrett LeSage</a> for creating the <a href="../blfs/artwork/lfsbanner.png">LFS banner</a>.</li>
   		<li><a href="mailto:nomis80@videotron.ca">Simon Perreault</a> for maintaining the Hints project.</li>
  
  
  
  1.29      +1 -1      www/people.html
  
  Index: people.html
  ===================================================================
  RCS file: /home/cvsroot/www/people.html,v
  retrieving revision 1.28
  retrieving revision 1.29
  diff -u -r1.28 -r1.29
  --- people.html	12 Sep 2003 08:53:38 -0000	1.28
  +++ people.html	12 Sep 2003 17:59:14 -0000	1.29
  @@ -141,7 +141,7 @@
   	</tr><tr>
   		<td>Mark Hymers</td>
   		<td><a href="http://linuxfromscratch.org/~markh/">markh</a></td>
  -		<td>BLFS initiator, former BLFS editor</td>
  +		<td>BLFS initiator, former BLFS and LFS editor</td>
   	</tr><tr>
   		<td>Seth W. Klein</td>
   		<td><a href="http://linuxfromscratch.org/~sklein/">sklein</a></td>
  
  
  
  1.38      +1 -1      www/hints/submit.html
  
  Index: submit.html
  ===================================================================
  RCS file: /home/cvsroot/www/hints/submit.html,v
  retrieving revision 1.37
  retrieving revision 1.38
  diff -u -r1.37 -r1.38
  --- submit.html	12 Sep 2003 15:32:40 -0000	1.37
  +++ submit.html	12 Sep 2003 17:59:14 -0000	1.38
  @@ -55,7 +55,7 @@
   	<li>Hints that have been integrated into the book will be retired after a stable version of the book is released.</li>
   	<li>Keep the file name of the hint short, but descriptive. The extension for the hint should be .txt. The name should be all lowercase.</li>
   	<li>The hint document is text based. The format for the hints is as explained at the end of this document.</li>
  -	<li>Avoid including scripts and patches in the hints. Keep these as separate files to avoid spoiling the beauty of the hint:) Patches should follow the <a href="http://patches.linuxfromscratch.org">patches format</a>. For all attachments for the hint, create a tarball that will untar into a directory that has the same name as the name of your hint (without the .txt extension). This tarball will be hosted in the download section for users to download. Patches for packages will also be hosted on Patches project website. For example, if your hint has a patch for gcc, that patch will be hosted under gcc directory. So be sure to mention the name of your hint in the patch description.</li>
  +	<li>Avoid including scripts and patches in the hints. Keep these as separate files to avoid spoiling the beauty of the hint:) Patches should follow the <a href="http://patches.linuxfromscratch.org">patches format</a>. For all attachments for the hint, created a tarball with the same name as your hint and that will untar into a directory that has the same name as the name of your hint (without the .txt extension). For example, if your hint is foo.txt, then the tarball would be named foo.tar.bz2 (replace compression extension by the one that you use) and it would untar into foo directory. This tarball will be hosted in the download section for users to download. Patches for packages will also be hosted on Patches project website. For example, if your hint has a patch for gcc, that patch will be hosted under gcc directory. So be sure to mention the name of your hint in the patch description.</li>
   	<li>To submit or update a hint, send an e-mail to the <a href="http://linuxfromscratch.org/mailman/listinfo/hints" title="Archive and subscription information for the hints mailinglist">hint mailing list</a>. From there it will be picked up by the hint maintainer, who will update the hint index and the tarball. To check if your hint has already been included, you can <a href="http://linuxfromscratch.org/mailman/listinfo/hints">subscribe</a> to the hints mailinglist and check for the CVS commit message. Keep the hints list solely for <strong>submitting hints and updates to hints</strong>.</li>
   </ul>
   
  
  
  



More information about the website mailing list