cvs commit: www/test/style advanced.css

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Wed Sep 3 02:33:43 PDT 2003


jeroen      03/09/03 03:33:43

  Modified:    test     website-bottom.html
               test/patches index-top.html
               test/style advanced.css
  Log:
  Applied Tushar's patch for the patches page. Minor color correction for the top links. And the usual spell fixes! :-)
  
  Revision  Changes    Path
  1.20      +1 -1      www/test/website-bottom.html
  
  Index: website-bottom.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/website-bottom.html,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- website-bottom.html	3 Sep 2003 01:30:09 -0000	1.19
  +++ website-bottom.html	3 Sep 2003 09:33:43 -0000	1.20
  @@ -4,7 +4,7 @@
   	<h3 id="todo">Todo</h3>
   
   	<h4>Dynamic newspages</h4>
  -		<p>Each section of lfs, blfs, hints and alfs have a news page. These should reflect the most current state of development which includes Bugzilla status, CVS commit logs and important maillinglist discussions. The result is useful as a development overview and reference point, both for the LFS team and for outside users. Currently the only thing missing are the Bugzilla messages:</p>
  +		<p>Each section of lfs, blfs, hints and alfs have a news page. These should reflect the most current state of development, which includes Bugzilla status, CVS commit logs and important maillinglist discussions. The result is useful as a development overview and reference point, both for the LFS team and for outside users. Currently the only things missing are the Bugzilla messages:</p>
   		<h5>Bugzilla script</h5>
   		<p>Write a script which feeds Bugzilla messages into the project's newspages. The information which needs to be extracted is the same (who, when and what bug is reported). Additionally, it should contain a link to the bug page. This script should be triggered whenever Bugzilla changes (a bug is added, resolved, commented etc.). This way, active LFS'ers can read the website daily, be aware of the current state of LFS and be able to directly comment on bugs. </p>
   		<p>Got some useful replies from the Bugzilla developers; it seems that <a href="http://bugzilla.mozilla.org/attachment.cgi?id=109161&action=view">fine_whine.pl</a> is usually used for this (described in <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=185090">bug 185090</a>). This script should at least be edited so it spits out content which we can use, similar to the solution we've devised for cvs2cl.pl.</p>
  
  
  
  1.2       +14 -9     www/test/patches/index-top.html
  
  Index: index-top.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/patches/index-top.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- index-top.html	2 Sep 2003 07:07:25 -0000	1.1
  +++ index-top.html	3 Sep 2003 09:33:43 -0000	1.2
  @@ -45,18 +45,19 @@
   <div id="pagenav">
   	<ul>
   		<li><a href="#info">General information</a></li>
  -		<li><a href="http://patches.linuxfromscratch.org">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>
  +		<li><b><a href="http://patches.linuxfromscratch.org/download/">Download patches</a></b></li>
   	</ul>
   </div>
   
   	<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="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>
  +		<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.</p>
   		<p>The patches project is maintained by <a href="http://www.jg555.com/">Jim Gifford</a> and <a href="http://www.linuxfromscratch.org/~tushar/">Tushar Teredesai</a>.</p>
   	
   	<h3 id="submit">Patches Submission Guidelines:</h3>
  @@ -74,7 +75,7 @@
   				<p><code>${packageName}-${packageVersion}-${patchName}-${patchVersion}.patch</code></p>
   				<dl>
   					<dt>packageName</dt>
  -						<dd>Official name of the package.</dd>
  +						<dd>Official name of the package. Be sure to follow the same capitalization that is followed by the official tarball for the package.</dd>
   					<dt>packageVersion</dt>
   						<dd>Version against which the patch applies.</dd>
   					<dt>patchName</dt>
  @@ -84,7 +85,7 @@
   				</dl>
   			</li>
   			<li>
  -				<p>The patch should have the following information, each item on a seperate line:</p>
  +				<p>The patch should have the following information, each item on a seperate line and in the same order (Be sure to follow the capitalization of the headers so that it is easier for scripts to parse the fields):</p>
   				<dl>
   					<dt>Submitted By</dt>
   						<dd>Name and/or E-mail of submitter.</dd>
  @@ -93,9 +94,9 @@
   					<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. Please keep this field short and restricted to a single line. A URI to a mailing-list discussion on the patch is the best fit for this field. Another option, if the patch is taken from a distro package is to write the name of the distribution and the package name (e.g. Redhat mozilla-1.4-12.src.rpm). If the patch is created by you and there is no URI to reference, just add your name in the field.</dd>
   					<dt>Description</dt>
  -						<dd>Description of what the patch does, links to discussion(s) related to the patch, etc.</dd>
  +						<dd>Description of what the patch does, links to more information related to the patch, etc. The more information you give to potential appliers of the patch, the better chance it has of being used. If you are modifying an existing patch, be sure to credit the original author.</dd>
   				</dl>
   				<p><em>Note: See the <a href="package-1.0-sample4patch.patch">sample patch</a>.</em></p>
   			</li>
  @@ -103,6 +104,7 @@
   			<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><em class="highlight">This should be possible once we have an autogenerated table.</em></p>
   		<ul>
  @@ -110,13 +112,15 @@
   			<li><a href="#">Sorted by submitter</a></li>
   			<li><a href="#">Sorted by date</a></li>
   		</ul>
  +-->
   
  +<!--
   	<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>
  +		<p>Create a script which creates a list of all directories in the CVS repositories and makes them into linkstable from the patches CVS repository. Extract information from the patch as follows and , like download location, patch submitter, date, origin and the short description/purpose. New entries should preferably be added to the top. </p>
   	<table>
   	<tbody>	
   		<tr>
  -			<th>Download location</th>
  +			<th>Name</th>
   			<th>Submitted By</th>
   			<th>Date</th>
   			<th>Origin</th>
  @@ -143,6 +147,7 @@
   	</tbody>
   	</table>
   	<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>
  
  
  
  1.12      +2 -2      www/test/style/advanced.css
  
  Index: advanced.css
  ===================================================================
  RCS file: /home/cvsroot/www/test/style/advanced.css,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- advanced.css	3 Sep 2003 01:30:09 -0000	1.11
  +++ advanced.css	3 Sep 2003 09:33:43 -0000	1.12
  @@ -73,9 +73,9 @@
   
   /* Layout styling */
   #header { background: #5e6e7e;}
  -#header a { color: #eee; font-size: 77%; text-decoration: none; border-bottom: 1px solid #eee;}
  +#header a { color: #fefefe; font-size: 77%; text-decoration: none; border-bottom: 1px solid #fefefe;}
   #header a:visited { color: #eee; text-decoration: none; border-bottom: none;}
  -#header a:hover { color: #e80; text-decoration: none; border-bottom: 1px solid #e80;}
  +#header a:hover { color: #e6ad04; text-decoration: none; border-bottom: 1px solid #e6ad04;}
   #header h2 a { display: none;}
   /* Technique from http://www.kryogenix.org/code/browser/lir/ */
   #body.root #header h1 { padding-top: 130px; width: 448px; background-image: url(../images/Craig_Colton5-448x130.png); background-repeat: no-repeat; overflow: hidden; height: 0px !important; height /**/:130px; }
  
  
  



More information about the website mailing list