cvs commit: www/test/patches index.html

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Fri Aug 29 02:12:19 PDT 2003


jeroen      03/08/29 03:12:19

  Modified:    test     cl2html.pl
               test/patches index.html
  Log:
  Updated cl2html.pl to fix a sorting bug. Applied Tushar's patch which updates the text of the patches project.
  
  Revision  Changes    Path
  1.2       +26 -21    www/test/cl2html.pl
  
  Index: cl2html.pl
  ===================================================================
  RCS file: /home/cvsroot/www/test/cl2html.pl,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- cl2html.pl	22 Aug 2003 19:15:35 -0000	1.1
  +++ cl2html.pl	29 Aug 2003 09:12:19 -0000	1.2
  @@ -24,7 +24,7 @@
   use Pod::Usage;
   use POSIX qw(strftime);
   
  -my $my_version = "0.1";
  +my $my_version = "0.2";
   
   # Convert ISO 8601 date (yyyy-mm-dd) to the specified format
   sub isodate2any {
  @@ -60,11 +60,23 @@
       exit 0;
   }
   
  -my $date = "";
  -my $buffer = "";
  -my $author = "";
  -my @messages = ();
  -my $files = "";
  +my $date = "";     # Current date
  +my $buffer = "";   # Current text in buffer
  +my $author = "";   # Current author
  +my @messages = (); # Commit messages of the same author
  +my $files = "";    # Files affected by CVS change
  +
  +sub print_log {
  +    print "<ul>\n\t<li>\n\t\t<h4>" . $author . " - " .
  +    isodate2any($date, '%Y/%m/%d') . "</h4>\n";
  +    print "\t\t<ul>\n";
  +    foreach (@messages) {
  +        print "\t\t\t<li>" . $_ . "</li>\n";
  +    }
  +    print "\t\t</ul>\n";
  +    print "\t</li>\n</ul>\n\n";
  +    @messages = ();
  +}
   
   my $parser = new XML::Parser(
       Handlers => {
  @@ -88,23 +100,12 @@
   sub handle_EndTag {
       my (undef, $tag) = @_;
   
  -    if ($tag eq "date" and $date ne $buffer) {
  -        if (@messages and $author and $date) {
  -            print "<ul>\n\t<li>\n\t\t<h4>" . $author . " - " .
  -            isodate2any($date, '%Y/%m/%d') . "</h4>\n";
  -            print "\t\t<ul>\n";
  -            foreach (@messages) {
  -                print "\t\t\t<li>" . $_ . "</li>\n";
  -            }
  -            print "\t\t</ul>\n";
  -            print "\t</li>\n</ul>\n\n";
  -            @messages = ();
  -            $date = "";
  -            $author = "";
  -        }
  +    if ($tag eq "date") {
  +        print_log() if ($buffer ne $date and @messages and $author and $date);
           $date = $buffer;
       }
  -    elsif ($tag eq "author" and $author ne $buffer) {
  +    elsif ($tag eq "author") {
  +        print_log() if ($buffer ne $author and @messages and $author and $date);
           $author = $buffer;
       }
       elsif ($tag eq "msg") {
  @@ -122,11 +123,15 @@
   
   sub handle_Text {
       my ($expat, $text) = @_;
  +
  +    # Encode "special" entities
       $text =~ s/\&/\&/g;
       $text =~ s/</\</g;
       $text =~ s/>/\>/g;
       #$text =~ s/\"/\"/g;
       #$text =~ s/\'/\'/g;
  +
  +    # Add current text to the buffer
       $buffer .= $text;
   }
   
  
  
  
  1.9       +10 -9     www/test/patches/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/patches/index.html,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- index.html	26 Aug 2003 05:46:17 -0000	1.8
  +++ index.html	29 Aug 2003 09:12:19 -0000	1.9
  @@ -54,16 +54,19 @@
   </div>
   
   	<h3 id="info">General information</h3>
  -		<p>The patches project and this webpage were created as a way for LFS and BLFS developers to easily submit and track patches for LFS and BLFS packages. It also serves as a testing ground for patches which may need to be included with the installation instructions for such packages. This page is not meant for regular or first-time LFS readers who wish to build a system by the book; they should adhere to the versions and patches which are in LFS or BLFS. </p>
  -		<p>The <a href="http://linuxfromscratch.org/mailman/listinfo/patches" title="Archive and subscription information for the patches mailinglist">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>
  +		<p>The patches project serves to be 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="http://linuxfromscratch.org/mailman/listinfo/patches" 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>
   	
   	<h3 id="submit">Patches Submission Guidelines:</h3>
  -		<p>Generally, we're interested in all patches which fix bugs or security issues with packages. At the moment, we're only interested in patches for packages which are in either LFS or BLFS.</p>
   		<ul>
   			<li>
  -				<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>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>
  +			</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>
   			</li>
   			<li>
   				<p>The patch file name should be in the following format:</p>
  @@ -95,17 +98,15 @@
   				</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="http://linuxfromscratch.org/mailman/listinfo/patches" title="Archive and subscription information for the patches mailinglist">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 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. 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="http://linuxfromscratch.org/mailman/listinfo/patches" 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="http://linuxfromscratch.org/mailman/listinfo/patches">the mailing list information page</a> for details on the mailing list.</p></li>
   		</ul>
   
   	<h3 id="browse">Browse patches</h3>
  -		<p>You can view the patches in a couple of ways:</p>
   		<ul>
   			<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>
   		</ul>
   
   	<h3 id="todo">Todo</h3>
  
  
  



More information about the website mailing list