cvs commit: www/test/patches index.html

Bill's LFS Login lfsbill at wlmcs.com
Tue Aug 19 06:30:23 PDT 2003


On Tue, 19 Aug 2003 jeroen at linuxfromscratch.org wrote:

> jeroen      03/08/19 07:05:16
>
>   Added:       test/patches index.html
>   Log:
>   Bring in the patches. Nowhere near complete to being a good frontend for the patches, but it's a start.
>
>   Revision  Changes    Path
>   1.1                  www/test/patches/index.html
>
>   Index: index.html
><snip>

>   		<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>

Wouldn't the "...of patches, discussion related to patches should be on
the appropriate support or development list; mostly this..." flow more
easily if it was broken up? Maybe something like

  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.

><snip>

>   				<p>The patch should have the following information each on a seperate line:</p>

   s/information each on/information, each item on/

or maybe

   s/information each on/information - each on/

><snip>

>   						<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>

s/put your name. the more/put your name. The more/

><snip>

>   			<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>

s/subission for archives/subission for the archives/

><snip>

HTH

-- 
Bill Maltby
lfsbill at wlmcs.com



More information about the website mailing list