cvs commit: www/patches submit.html

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Sat Oct 25 04:52:03 PDT 2003


jeroen      03/10/25 05:52:03

  Modified:    lfs      news-2003.txt
               patches  submit.html
  Log:
  Update ALFS-LFS-5.0pre2 profile location. Fix a couple of spell errors on the patches site.
  
  Revision  Changes    Path
  1.38      +1 -1      www/lfs/news-2003.txt
  
  Index: news-2003.txt
  ===================================================================
  RCS file: /home/cvsroot/www/lfs/news-2003.txt,v
  retrieving revision 1.37
  retrieving revision 1.38
  diff -u -r1.37 -r1.38
  --- news-2003.txt	25 Oct 2003 04:30:27 -0000	1.37
  +++ news-2003.txt	25 Oct 2003 11:52:03 -0000	1.38
  @@ -18,7 +18,7 @@
   Date: 2003/10/07
   
   		<p>David Wheeler was kind enough to provide the nALFS development team a copy of his LFS 5.0-PRE2 profile.</p>
  -		<p>If you are interested in trying it out, you can download it from <a href="http://downloads.linuxfromscratch.org/alfs/nALFS-LFS-5.0-profile.tar.bz2">http://downloads.linuxfromscratch.org/alfs/nALFS-LFS-5.0-profile.tar.bz2</a>.</p>
  +		<p>If you are interested in trying it out, you can <a href="alfs/downloads/profiles/profile-LFS-5.0-pre2.tar.bz2">download</a> it.</p>
   		<p>Be sure to read the README file in the root of the archive for instructions.</p>
   		<p>We would appreciate any feedback on this profile. Any and all feedback can be sent to the <a href="http://www.linuxfromscratch.org/mailman/listinfo/alfs-discuss/">alfs-discuss</a> mailinglist.</p>
   
  
  
  
  1.8       +2 -2      www/patches/submit.html
  
  Index: submit.html
  ===================================================================
  RCS file: /home/cvsroot/www/patches/submit.html,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- submit.html	9 Oct 2003 10:08:12 -0000	1.7
  +++ submit.html	25 Oct 2003 11:52:03 -0000	1.8
  @@ -60,12 +60,12 @@
   <h2 id="submit">Patches Submission Guidelines:</h2>
   <ul>
   	<li>
  -		<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>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 maintainers will copy the file over to the new version.</p>
   	</li>
   	<li>
   		<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>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 instructions in the book.</p>
   	</li>
   	<li>
   		<p>The patch file name should be in the following format:</p>
  
  
  



More information about the website mailing list