From carolyn93@example.net Tue Sep 16 13:05:57 2008
Return-Path: <carolyn93@example.net>
Delivered-To: carolyn93@example.net
Received: (qmail 62486 invoked from network); 16 Sep 2008 13:05:57 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155)
  by minotaur.apache.org with SMTP; 16 Sep 2008 13:05:57 -0000
Received: (qmail 72995 invoked by uid 500); 16 Sep 2008 13:05:46 -0000
Delivered-To: carolyn93@example.net
Received: (qmail 72912 invoked by uid 500); 16 Sep 2008 13:05:45 -0000
Mailing-List: contact carolyn93@example.net; run by ezmlm
Precedence: bulk
list-help: <mailto:carolyn93@example.net>
list-unsubscribe: <mailto:carolyn93@example.net>
List-Post: <mailto:carolyn93@example.net>
Reply-To: carolyn93@example.net
List-Id: <docs.httpd.apache.org>
Delivered-To: mailing list carolyn93@example.net
Received: (qmail 72888 invoked by uid 99); 16 Sep 2008 13:05:45 -0000
Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2008 06:05:45 -0700
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: 83.161.120.155 is neither permitted nor denied by domain of carolyn93@example.net)
Received: from [83.161.120.155] (HELO cdptpa-omtalb.mail.rr.com) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2008 13:04:46 +0000
Received: from tick.localdomain ([83.161.120.155])
          by cdptpa-omta06.mail.rr.com with ESMTP
          id <carolyn93@example.net>;
          Tue, 16 Sep 2008 13:05:10 +0000
Received: by tick.localdomain (Postfix, from userid 5001)
	id 86658B5C129; Mon, 15 Sep 2008 09:38:40 -0400 (EDT)
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on tick.mynet
X-Spam-Level: 
Received: from danpoirier.homeunix.org (localhost [83.161.120.155])
	by tick.localdomain (Postfix) with ESMTP id 174BBB5C0E2;
	Mon, 15 Sep 2008 09:37:52 -0400 (EDT)
Received: from 83.161.120.155
        (SquirrelMail authenticated user poirier)
        by danpoirier.homeunix.org with HTTP;
        Mon, 15 Sep 2008 09:37:52 -0400 (EDT)
Message-ID: <carolyn93@example.net>
Date: Mon, 15 Sep 2008 09:37:52 -0400 (EDT)
Subject: [PATCH] grammar for mod_sed
From: "Dan Poirier" <carolyn93@example.net>
To: carolyn93@example.net
User-Agent: SquirrelMail/1.4.15
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Checked: Checked by ClamAV on apache.org
X-Old-Spam-Status: No, score=-4.4 required=2.0 tests=ALL_TRUSTED,BAYES_00
	autolearn=ham version=3.2.5

This patch suggests some grammar improvements for mod_sed.  No substantive
changes.

Dan Poirier
carolyn93@example.net

Index: docs/manual/mod/mod_sed.xml
===================================================================
--- docs/manual/mod/mod_sed.xml	(revision 695466)
+++ docs/manual/mod/mod_sed.xml	(working copy)
@@ -29,38 +29,38 @@

 <summary>
 <p>
-mod_sed is a in-process content filter. mod_sed filter implement the sed
edit
-commands implemented by Solaris 10 sed
-program as described in <a
href="http://docs.sun.com/app/docs/doc/816-5165/sed-1b?a=view">man
-page</a>. However unlike sed, mod_sed doesn't take data from
+mod_sed is an in-process content filter. The mod_sed filter implements
the sed edit
+commands implemented by the Solaris 10 sed
+program as described in the <a
href="http://docs.sun.com/app/docs/doc/816-5165/sed-1b?a=view">man
+page</a>. However, unlike sed, mod_sed doesn't take data from
 standard
-input. Instead filter act on the entity data sent between client and
-server. mod_sed can be used as a input or output filter. mod_sed is a
-content filter which means that it can not be used to modify client or
+input. Instead, the filter acts on the entity data sent between client and
+server. mod_sed can be used as an input or output filter. mod_sed is a
+content filter, which means that it cannot be used to modify client or
 server http headers.
 </p>
 <p>
-mod_sed output filter accept a chunk of data and execute the sed scripts
on data and generates the output which is passed to next filter in the
filter chain.
+The mod_sed output filter accepts a chunk of data, executes the sed
scripts on the data, and generates the output which is passed to next
filter in the filter chain.
 </p>

 <p>
-mod_sed input filter reads the data from next filter in filter chain and
executes the sed scripts and returns the generated data to caller filter
in the filter chain.
+The mod_sed input filter reads the data from the next filter in filter
chain, executes the sed scripts, and returns the generated data to the
caller filter in the filter chain.
 </p>

 <p>
-Both input and output filter only process the data if new line character
is seen in the content. At the end of the data, rest of the data is
treated as last line.
+Both the input and output filter only process the data if new line
characters are seen in the content. At the end of the data, the rest of
the data is treated as the last line.
 </p>

 <p>A tutorial article on mod_sed, and why it is more powerful than simple
-string or regular expression search and replace, is available in <a
+string or regular expression search and replace, is available <a
 href="http://blogs.sun.com/basant/entry/using_mod_sed_to_filter">on
 the author's blog</a>.</p>

 </summary>

 <section id="sampleconf"><title>Sample Configuration</title>
-    <example><title>Adding a output filter </title>
-         # In following example, sed filter will replace the string <br />
+    <example><title>Adding an output filter </title>
+         # In following example, the sed filter will change the string
<br />
          # "monday" to "MON" and the string "sunday" to SUN in html
document <br />
          # before sending to client. <br />
         <indent>
@@ -74,8 +74,8 @@
         </indent>
     </example>

-    <example><title>Adding a input filter </title>
-         # In following example, sed filter will replace the string <br />
+    <example><title>Adding an input filter </title>
+         # In following example, the sed filter will change the string
<br />
          # "monday" to "MON" and the string "sunday" to SUN in the POST
data <br />
          # sent to php <br />
         <indent>
@@ -91,7 +91,7 @@
 </section>
 <section id="sed_commands"><title>Sed Commands</title>
     <p>
-    Complete details of the sed command can be found from
+    Complete details of the sed command can be found from the
    <a href="http://docs.sun.com/app/docs/doc/816-5165/sed-1b?a=view">sed man
 page</a>.
     </p>
@@ -99,27 +99,27 @@
         <dt><code>b</code></dt>
         <dd>branch to the label specified (Similar to goto)</dd>
         <dt><code>h</code></dt>
-        <dd>Copy the current line to hold buffer.</dd>
+        <dd>Copy the current line to the hold buffer.</dd>
         <dt><code>H</code></dt>
-        <dd>Append the current line to hold buffer.</dd>
+        <dd>Append the current line to the hold buffer.</dd>
         <dt><code>g</code></dt>
         <dd>Copy the hold buffer into the current line</dd>
         <dt><code>G</code></dt>
-        <dd>Append the hold buffer into the current line</dd>
+        <dd>Append the hold buffer to the current line</dd>
         <dt><code>x</code></dt>
-        <dd>Swap the content of hold buffer and current line</dd>
+        <dd>Swap the content of the hold buffer and the current line</dd>
     </dl>
 </section>

 <directivesynopsis>
 <name>OutputSed</name>
-<description>Sed command for filter the response content</description>
+<description>Sed command for filtering the response content</description>
 <syntax>OutputSed <var>sed-command</var></syntax>
 <contextlist><context>directory</context><context>.htaccess</context>
 </contextlist>

 <usage>
-    <p>The <directive>OutputSed</directive> directive specify the sed
+    <p>The <directive>OutputSed</directive> directive specifies the sed
     command which will be executed on the response.
     </p>
 </usage>
@@ -133,7 +133,7 @@
 </contextlist>

 <usage>
-    <p>The <directive>InputSed</directive> directive specify the sed command
+    <p>The <directive>InputSed</directive> directive specifies the sed
command
     which will be executed on the request data e.g POST data.
     </p>
 </usage>



---------------------------------------------------------------------
To unsubscribe, e-mail: carolyn93@example.net
For additional commands, e-mail: carolyn93@example.net


From carolyn93@example.net Tue Sep 16 13:21:00 2008
Return-Path: <carolyn93@example.net>
Delivered-To: carolyn93@example.net
Received: (qmail 72768 invoked from network); 16 Sep 2008 13:20:57 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155)
  by minotaur.apache.org with SMTP; 16 Sep 2008 13:20:57 -0000
Received: (qmail 99752 invoked by uid 500); 16 Sep 2008 13:20:53 -0000
Delivered-To: carolyn93@example.net
Received: (qmail 99582 invoked by uid 500); 16 Sep 2008 13:20:52 -0000
Mailing-List: contact carolyn93@example.net; run by ezmlm
Precedence: bulk
list-help: <mailto:carolyn93@example.net>
list-unsubscribe: <mailto:carolyn93@example.net>
List-Post: <mailto:carolyn93@example.net>
Reply-To: carolyn93@example.net
List-Id: <docs.httpd.apache.org>
Delivered-To: mailing list carolyn93@example.net
Received: (qmail 99564 invoked by uid 99); 16 Sep 2008 13:20:52 -0000
Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2008 06:20:52 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of carolyn93@example.net designates 83.161.120.155 as permitted sender)
Received: from [83.161.120.155] (HELO sasl.smtp.pobox.com) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2008 13:19:53 +0000
Received: from localhost.localdomain (localhost [83.161.120.155])
	by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id 4D0A6627C9
	for <carolyn93@example.net>; Tue, 16 Sep 2008 09:19:53 -0400 (EDT)
Received: from [83.161.120.155] (bi01p1.nc.us.ibm.com [83.161.120.155]) (using
 TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate
 requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id
 05463627C8 for <carolyn93@example.net>; Tue, 16 Sep 2008 09:19:52 -0400 (EDT)
Message-ID: <carolyn93@example.net>
Date: Tue, 16 Sep 2008 09:19:51 -0400
From: Dan Poirier <carolyn93@example.net>
User-Agent: Thunderbird 83.161.120.155 (X11/20080724)
MIME-Version: 1.0
To: carolyn93@example.net
Subject: Re: [PATCH] grammar for mod_sed
References:
 <carolyn93@example.net>
In-Reply-To:
 <carolyn93@example.net>
Content-Type: multipart/mixed; boundary="------------030803020206080604070902"
X-Pobox-Relay-ID:
 25F32E0E-83F2-11DD-B92A-D0CFFE4BC1C1-25076293!a-sasl-fastnet.pobox.com
X-Virus-Checked: Checked by ClamAV on apache.org

--------------030803020206080604070902
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sorry, here it is again as an attachment.



--------------030803020206080604070902
Content-Type: text/plain;
 name="mod_sed.patch1.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="mod_sed.patch1.txt"

Index: docs/manual/mod/mod_sed.xml
===================================================================
--- docs/manual/mod/mod_sed.xml	(revision 695466)
+++ docs/manual/mod/mod_sed.xml	(working copy)
@@ -29,38 +29,38 @@
 
 <summary>
 <p>
-mod_sed is a in-process content filter. mod_sed filter implement the sed edit
-commands implemented by Solaris 10 sed
-program as described in <a href="http://docs.sun.com/app/docs/doc/816-5165/sed-1b?a=view">man
-page</a>. However unlike sed, mod_sed doesn't take data from
+mod_sed is an in-process content filter. The mod_sed filter implements the sed edit
+commands implemented by the Solaris 10 sed
+program as described in the <a href="http://docs.sun.com/app/docs/doc/816-5165/sed-1b?a=view">man
+page</a>. However, unlike sed, mod_sed doesn't take data from
 standard
-input. Instead filter act on the entity data sent between client and
-server. mod_sed can be used as a input or output filter. mod_sed is a
-content filter which means that it can not be used to modify client or
+input. Instead, the filter acts on the entity data sent between client and
+server. mod_sed can be used as an input or output filter. mod_sed is a
+content filter, which means that it cannot be used to modify client or
 server http headers.
 </p>
 <p>
-mod_sed output filter accept a chunk of data and execute the sed scripts on data and generates the output which is passed to next filter in the filter chain.
+The mod_sed output filter accepts a chunk of data, executes the sed scripts on the data, and generates the output which is passed to next filter in the filter chain.
 </p>
 
 <p>
-mod_sed input filter reads the data from next filter in filter chain and executes the sed scripts and returns the generated data to caller filter in the filter chain.
+The mod_sed input filter reads the data from the next filter in filter chain, executes the sed scripts, and returns the generated data to the caller filter in the filter chain.
 </p>
 
 <p>
-Both input and output filter only process the data if new line character is seen in the content. At the end of the data, rest of the data is treated as last line.
+Both the input and output filter only process the data if new line characters are seen in the content. At the end of the data, the rest of the data is treated as the last line.
 </p>
 
 <p>A tutorial article on mod_sed, and why it is more powerful than simple
-string or regular expression search and replace, is available in <a
+string or regular expression search and replace, is available <a
 href="http://blogs.sun.com/basant/entry/using_mod_sed_to_filter">on
 the author's blog</a>.</p>
 
 </summary>
 
 <section id="sampleconf"><title>Sample Configuration</title>
-    <example><title>Adding a output filter </title>
-         # In following example, sed filter will replace the string <br />
+    <example><title>Adding an output filter </title>
+         # In following example, the sed filter will change the string <br />
          # "monday" to "MON" and the string "sunday" to SUN in html document <br />
          # before sending to client. <br />
         <indent>
@@ -74,8 +74,8 @@
         </indent>
     </example>
 
-    <example><title>Adding a input filter </title>
-         # In following example, sed filter will replace the string <br />
+    <example><title>Adding an input filter </title>
+         # In following example, the sed filter will change the string <br />
          # "monday" to "MON" and the string "sunday" to SUN in the POST data <br />
          # sent to php <br />
         <indent>
@@ -91,7 +91,7 @@
 </section>
 <section id="sed_commands"><title>Sed Commands</title>
     <p>
-    Complete details of the sed command can be found from
+    Complete details of the sed command can be found from the
    <a href="http://docs.sun.com/app/docs/doc/816-5165/sed-1b?a=view">sed man
 page</a>.
     </p>
@@ -99,27 +99,27 @@
         <dt><code>b</code></dt>
         <dd>branch to the label specified (Similar to goto)</dd>
         <dt><code>h</code></dt>
-        <dd>Copy the current line to hold buffer.</dd>
+        <dd>Copy the current line to the hold buffer.</dd>
         <dt><code>H</code></dt>
-        <dd>Append the current line to hold buffer.</dd>
+        <dd>Append the current line to the hold buffer.</dd>
         <dt><code>g</code></dt>
         <dd>Copy the hold buffer into the current line</dd>
         <dt><code>G</code></dt>
-        <dd>Append the hold buffer into the current line</dd>
+        <dd>Append the hold buffer to the current line</dd>
         <dt><code>x</code></dt>
-        <dd>Swap the content of hold buffer and current line</dd>
+        <dd>Swap the content of the hold buffer and the current line</dd>
     </dl>
 </section>
 
 <directivesynopsis>
 <name>OutputSed</name>
-<description>Sed command for filter the response content</description>
+<description>Sed command for filtering the response content</description>
 <syntax>OutputSed <var>sed-command</var></syntax>
 <contextlist><context>directory</context><context>.htaccess</context>
 </contextlist>
 
 <usage>
-    <p>The <directive>OutputSed</directive> directive specify the sed
+    <p>The <directive>OutputSed</directive> directive specifies the sed
     command which will be executed on the response.
     </p>
 </usage>
@@ -133,7 +133,7 @@
 </contextlist>
 
 <usage>
-    <p>The <directive>InputSed</directive> directive specify the sed command
+    <p>The <directive>InputSed</directive> directive specifies the sed command
     which will be executed on the request data e.g POST data.
     </p>
 </usage>


--------------030803020206080604070902
Content-Type: text/plain; charset=us-ascii

---------------------------------------------------------------------
To unsubscribe, e-mail: carolyn93@example.net
For additional commands, e-mail: carolyn93@example.net
--------------030803020206080604070902--

From carolyn93@example.net Tue Sep 16 15:37:31 2008
Return-Path: <carolyn93@example.net>
Delivered-To: carolyn93@example.net
Received: (qmail 78422 invoked from network); 16 Sep 2008 15:37:31 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155)
  by minotaur.apache.org with SMTP; 16 Sep 2008 15:37:31 -0000
Received: (qmail 76514 invoked by uid 500); 16 Sep 2008 15:37:27 -0000
Delivered-To: carolyn93@example.net
Received: (qmail 76489 invoked by uid 500); 16 Sep 2008 15:37:27 -0000
Mailing-List: contact carolyn93@example.net; run by ezmlm
Precedence: bulk
list-help: <mailto:carolyn93@example.net>
list-unsubscribe: <mailto:carolyn93@example.net>
List-Post: <mailto:carolyn93@example.net>
Reply-To: carolyn93@example.net
List-Id: <docs.httpd.apache.org>
Delivered-To: mailing list carolyn93@example.net
Received: (qmail 76478 invoked by uid 99); 16 Sep 2008 15:37:27 -0000
Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2008 08:37:27 -0700
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [83.161.120.155] (HELO smarthost03.mail.zen.net.uk) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2008 15:36:25 +0000
Received: from [83.161.120.155] (helo=[83.161.120.155])
	by smarthost03.mail.zen.net.uk with esmtp (Exim 4.63)
	(envelope-from <carolyn93@example.net>)
	id 1Kfcbo-00023X-Qp
	for carolyn93@example.net; Tue, 16 Sep 2008 15:36:56 +0000
Message-ID: <carolyn93@example.net>
Date: Tue, 16 Sep 2008 16:36:52 +0100
From: Tony Stevenson <carolyn93@example.net>
User-Agent: Thunderbird 83.161.120.155 (Windows/20080708)
MIME-Version: 1.0
To: carolyn93@example.net
Subject: Re: [PATCH] grammar for mod_sed
References: <carolyn93@example.net> <carolyn93@example.net>
In-Reply-To: <carolyn93@example.net>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Originating-Smarthost03-IP: [83.161.120.155]
X-Virus-Checked: Checked by ClamAV on apache.org

Dan Poirier wrote:
> Sorry, here it is again as an attachment.
> 

Dan,

Thanks for the patch.  I have committed to the /trunk/ branch.
See here ->  http://svn.apache.org/viewvc?rev=695942&view=rev




-- 


-----------------------------------------
Tony Stevenson
carolyn93@example.net  //  carolyn93@example.net
http://www.pc-tony.com/

1024D/51047D66 ECAF DC55 C608 5E82 0B5E  3359 C9C7 924E 5104 7D66
-----------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: carolyn93@example.net
For additional commands, e-mail: carolyn93@example.net


From carolyn93@example.net Mon Sep 29 13:07:40 2008
Return-Path: <carolyn93@example.net>
Delivered-To: carolyn93@example.net
Received: (qmail 10343 invoked from network); 29 Sep 2008 13:07:40 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155)
  by minotaur.apache.org with SMTP; 29 Sep 2008 13:07:40 -0000
Received: (qmail 44075 invoked by uid 500); 29 Sep 2008 13:07:38 -0000
Delivered-To: carolyn93@example.net
Received: (qmail 44038 invoked by uid 500); 29 Sep 2008 13:07:37 -0000
Mailing-List: contact carolyn93@example.net; run by ezmlm
Precedence: bulk
list-help: <mailto:carolyn93@example.net>
list-unsubscribe: <mailto:carolyn93@example.net>
List-Post: <mailto:carolyn93@example.net>
Reply-To: carolyn93@example.net
List-Id: <docs.httpd.apache.org>
Delivered-To: mailing list carolyn93@example.net
Received: (qmail 44027 invoked by uid 99); 29 Sep 2008 13:07:37 -0000
Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Sep 2008 06:07:37 -0700
X-ASF-Spam-Status: No, hits=2.0 required=10.0
	tests=HTML_MESSAGE,HTML_NONELEMENT_40_50,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF carolyn93@example.net)
Received: from [83.161.120.155] (HELO web7604.mail.in.yahoo.com) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with SMTP; Mon, 29 Sep 2008 13:06:33 +0000
Received: (qmail 25320 invoked by uid 60001); 29 Sep 2008 13:07:04 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.co.in;
  h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
  b=vYusnSjpFMQ1IMCwQstL62gfvm4MFoze+3J2sPMgFdytnsnUWy77MAnpxyES9o87nujfQpjBCmOJmlSGQoAXCf7zdUEKx6lktOKk6fAhKVdx7w4mBaHuvaXVUxmVp9crHk1n8wvzPRunx6Pbe7aoZIDkIN3XDyUoTcR268ybxnU=;
X-YMail-OSG: r9fN08EVM1mdpfZnD3JGmPIN2wsPn35lAxnVd8tSIci5VKSSVNG.ZmT2zUv9fOTPLrPZn2yePFyyX_5uW0A.JhIM5ArVYIQwSngLZEVu6uZlut32agq_0F4Jh4Oh8iCN9FlgSIivqc79C20Q3fsUUg9r
Received: from [83.161.120.155] by web7604.mail.in.yahoo.com via HTTP; Mon, 29 Sep 2008 14:07:04 BST
Date: Mon, 29 Sep 2008 14:07:04 +0100 (BST)
From: mani vel <carolyn93@example.net>
Subject: Re: [PATCH] grammar for mod_sed
To: carolyn93@example.net
In-Reply-To: <carolyn93@example.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-611433841-1222693624=:25259"
Content-Transfer-Encoding: 8bit
Message-ID: <carolyn93@example.net>
X-Virus-Checked: Checked by ClamAV on apache.org

--0-611433841-1222693624=:25259
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

this is virus dont sent

Dan Poirier <carolyn93@example.net> wrote:  This patch suggests some grammar improvements for mod_sed. No substantive
changes.

Dan Poirier
carolyn93@example.net

Index: docs/manual/mod/mod_sed.xml
===================================================================
--- docs/manual/mod/mod_sed.xml (revision 695466)
+++ docs/manual/mod/mod_sed.xml (working copy)
@@ -29,38 +29,38 @@


  
-mod_sed is a in-process content filter. mod_sed filter implement the sed
edit
-commands implemented by Solaris 10 sed
-program as described in href="http://docs.sun.com/app/docs/doc/816-5165/sed-1b?a=view">man
-page. However unlike sed, mod_sed doesn't take data from
+mod_sed is an in-process content filter. The mod_sed filter implements
the sed edit
+commands implemented by the Solaris 10 sed
+program as described in the href="http://docs.sun.com/app/docs/doc/816-5165/sed-1b?a=view">man
+page. However, unlike sed, mod_sed doesn't take data from
standard
-input. Instead filter act on the entity data sent between client and
-server. mod_sed can be used as a input or output filter. mod_sed is a
-content filter which means that it can not be used to modify client or
+input. Instead, the filter acts on the entity data sent between client and
+server. mod_sed can be used as an input or output filter. mod_sed is a
+content filter, which means that it cannot be used to modify client or
server http headers.


  
-mod_sed output filter accept a chunk of data and execute the sed scripts
on data and generates the output which is passed to next filter in the
filter chain.
+The mod_sed output filter accepts a chunk of data, executes the sed
scripts on the data, and generates the output which is passed to next
filter in the filter chain.



  
-mod_sed input filter reads the data from next filter in filter chain and
executes the sed scripts and returns the generated data to caller filter
in the filter chain.
+The mod_sed input filter reads the data from the next filter in filter
chain, executes the sed scripts, and returns the generated data to the
caller filter in the filter chain.



  
-Both input and output filter only process the data if new line character
is seen in the content. At the end of the data, rest of the data is
treated as last line.
+Both the input and output filter only process the data if new line
characters are seen in the content. At the end of the data, the rest of
the data is treated as the last line.



  A tutorial article on mod_sed, and why it is more powerful than simple
-string or regular expression search and replace, is available in +string or regular expression search and replace, is available href="http://blogs.sun.com/basant/entry/using_mod_sed_to_filter">on
the author's blog.





- 
- # In following example, sed filter will replace the string 

+ 
+ # In following example, the sed filter will change the string


# "monday" to "MON" and the string "sunday" to SUN in html
document 

# before sending to client. 


@@ -74,8 +74,8 @@



- 
- # In following example, sed filter will replace the string 

+ 
+ # In following example, the sed filter will change the string


# "monday" to "MON" and the string "sunday" to SUN in the POST
data 

# sent to php 


@@ -91,7 +91,7 @@


  
- Complete details of the sed command can be found from
+ Complete details of the sed command can be found from the
sed man
page.


@@ -99,27 +99,27 @@
  
b
  
   branch to the label specified (Similar to goto)
  
h
-   
   Copy the current line to hold buffer.
+   
   Copy the current line to the hold buffer.
  
H
-   
   Append the current line to hold buffer.
+   
   Append the current line to the hold buffer.
  
g
  
   Copy the hold buffer into the current line
  
G
-   
   Append the hold buffer into the current line
+   
   Append the hold buffer to the current line
  
x
-   
   Swap the content of hold buffer and current line
+   
   Swap the content of the hold buffer and the current line
  



OutputSed
-Sed command for filter the response content
+Sed command for filtering the response content
OutputSed sed-command
directory.htaccess



-   The OutputSed directive specify the sed
+   The OutputSed directive specifies the sed
command which will be executed on the response.



@@ -133,7 +133,7 @@



-   The InputSed directive specify the sed command
+   The InputSed directive specifies the sed
command
which will be executed on the request data e.g POST data.






---------------------------------------------------------------------
To unsubscribe, e-mail: carolyn93@example.net
For additional commands, e-mail: carolyn93@example.net



       
---------------------------------
 Unlimited freedom, unlimited storage. Get it now
--0-611433841-1222693624=:25259
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

this is virus dont sent<BR><BR><B><I>Dan Poirier &lt;carolyn93@example.net&gt;</I></B> wrote:  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">This patch suggests some grammar improvements for mod_sed. No substantive<BR>changes.<BR><BR>Dan Poirier<BR>carolyn93@example.net<BR><BR>Index: docs/manual/mod/mod_sed.xml<BR>===================================================================<BR>--- docs/manual/mod/mod_sed.xml (revision 695466)<BR>+++ docs/manual/mod/mod_sed.xml (working copy)<BR>@@ -29,38 +29,38 @@<BR><BR><SUMMARY><BR>  <div><BR>-mod_sed is a in-process content filter. mod_sed filter implement the sed<BR>edit<BR>-commands implemented by Solaris 10 sed<BR>-program as described in <A<BR>href="http://docs.sun.com/app/docs/doc/816-5165/sed-1b?a=view"&gt;man<BR>-page</A>. However unlike sed, mod_sed doesn't take data from<BR>+mod_sed is an in-process content filter. The mod_sed filter implements<BR>the sed edit<BR>+commands
 implemented by the Solaris 10 sed<BR>+program as described in the <A<BR>href="http://docs.sun.com/app/docs/doc/816-5165/sed-1b?a=view"&gt;man<BR>+page</A>. However, unlike sed, mod_sed doesn't take data from<BR>standard<BR>-input. Instead filter act on the entity data sent between client and<BR>-server. mod_sed can be used as a input or output filter. mod_sed is a<BR>-content filter which means that it can not be used to modify client or<BR>+input. Instead, the filter acts on the entity data sent between client and<BR>+server. mod_sed can be used as an input or output filter. mod_sed is a<BR>+content filter, which means that it cannot be used to modify client or<BR>server http headers.<BR></div><BR>  <div><BR>-mod_sed output filter accept a chunk of data and execute the sed scripts<BR>on data and generates the output which is passed to next filter in the<BR>filter chain.<BR>+The mod_sed output filter accepts a chunk of data, executes the sed<BR>scripts on the data, and
 generates the output which is passed to next<BR>filter in the filter chain.<BR></div><BR><BR>  <div><BR>-mod_sed input filter reads the data from next filter in filter chain and<BR>executes the sed scripts and returns the generated data to caller filter<BR>in the filter chain.<BR>+The mod_sed input filter reads the data from the next filter in filter<BR>chain, executes the sed scripts, and returns the generated data to the<BR>caller filter in the filter chain.<BR></div><BR><BR>  <div><BR>-Both input and output filter only process the data if new line character<BR>is seen in the content. At the end of the data, rest of the data is<BR>treated as last line.<BR>+Both the input and output filter only process the data if new line<BR>characters are seen in the content. At the end of the data, the rest of<BR>the data is treated as the last line.<BR></div><BR><BR>  <div>A tutorial article on mod_sed, and why it is more powerful than simple<BR>-string or regular expression search
 and replace, is available in <A<BR>+string or regular expression search and replace, is available <A<BR>href="http://blogs.sun.com/basant/entry/using_mod_sed_to_filter"&gt;on<BR>the author's blog</A>.</div><BR><BR></SUMMARY><BR><BR><SECTION id=sampleconf><BR>- <EXAMPLE><BR>- # In following example, sed filter will replace the string <BR><BR>+ <EXAMPLE><BR>+ # In following example, the sed filter will change the string<BR><BR><BR># "monday" to "MON" and the string "sunday" to SUN in html<BR>document <BR><BR># before sending to client. <BR><BR><INDENT><BR>@@ -74,8 +74,8 @@<BR></INDENT><BR></EXAMPLE><BR><BR>- <EXAMPLE><BR>- # In following example, sed filter will replace the string <BR><BR>+ <EXAMPLE><BR>+ # In following example, the sed filter will change the string<BR><BR><BR># "monday" to "MON" and the string "sunday" to SUN in the POST<BR>data <BR><BR># sent to php <BR><BR><INDENT><BR>@@ -91,7 +91,7 @@<BR></SECTION><BR><SECTION id=sed_commands><BR>  <div><BR>- Complete
 details of the sed command can be found from<BR>+ Complete details of the sed command can be found from the<BR><A href="http://docs.sun.com/app/docs/doc/816-5165/sed-1b?a=view">sed man<BR>page</A>.<BR></div><BR>@@ -99,27 +99,27 @@<BR>  <DT><CODE>b</CODE></DT><BR>  <DD>branch to the label specified (Similar to goto)</DD><BR>  <DT><CODE>h</CODE></DT><BR>-   <DD>Copy the current line to hold buffer.</DD><BR>+   <DD>Copy the current line to the hold buffer.</DD><BR>  <DT><CODE>H</CODE></DT><BR>-   <DD>Append the current line to hold buffer.</DD><BR>+   <DD>Append the current line to the hold buffer.</DD><BR>  <DT><CODE>g</CODE></DT><BR>  <DD>Copy the hold buffer into the current line</DD><BR>  <DT><CODE>G</CODE></DT><BR>-   <DD>Append the hold buffer into the current line</DD><BR>+   <DD>Append the hold buffer to the current line</DD><BR>  <DT><CODE>x</CODE></DT><BR>-   <DD>Swap the content of hold buffer and current line</DD><BR>+   <DD>Swap the content of the hold buffer and
 the current line</DD><BR>  <DL></DL><BR></SECTION><BR><BR><DIRECTIVESYNOPSIS><BR><NAME>OutputSed</NAME><BR>-<DESCRIPTION>Sed command for filter the response content</DESCRIPTION><BR>+<DESCRIPTION>Sed command for filtering the response content</DESCRIPTION><BR><SYNTAX>OutputSed <VAR>sed-command</VAR></SYNTAX><BR><CONTEXTLIST><CONTEXT>directory</CONTEXT><CONTEXT>.htaccess</CONTEXT><BR></CONTEXTLIST><BR><BR><USAGE><BR>-   <div>The <DIRECTIVE>OutputSed</DIRECTIVE> directive specify the sed<BR>+   <div>The <DIRECTIVE>OutputSed</DIRECTIVE> directive specifies the sed<BR>command which will be executed on the response.<BR></div><BR></USAGE><BR>@@ -133,7 +133,7 @@<BR></CONTEXTLIST><BR><BR><USAGE><BR>-   <div>The <DIRECTIVE>InputSed</DIRECTIVE> directive specify the sed command<BR>+   <div>The <DIRECTIVE>InputSed</DIRECTIVE> directive specifies the sed<BR>command<BR>which will be executed on the request data e.g POST
 data.<BR></div><BR></USAGE><BR><BR><BR><BR>---------------------------------------------------------------------<BR>To unsubscribe, e-mail: carolyn93@example.net<BR>For additional commands, e-mail: carolyn93@example.net<BR><BR></BLOCKQUOTE><BR><p>&#32;



      <!--2--><hr size=1></hr> Unlimited freedom, unlimited storage. <a href="http://in.rd.yahoo.com/tagline_mail_2/*http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/">Get it now</a>
--0-611433841-1222693624=:25259--

From carolyn93@example.net Mon Sep 29 14:28:57 2008
Return-Path: <carolyn93@example.net>
Delivered-To: carolyn93@example.net
Received: (qmail 64296 invoked from network); 29 Sep 2008 14:28:57 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155)
  by minotaur.apache.org with SMTP; 29 Sep 2008 14:28:57 -0000
Received: (qmail 17451 invoked by uid 500); 29 Sep 2008 14:28:53 -0000
Delivered-To: carolyn93@example.net
Received: (qmail 17416 invoked by uid 500); 29 Sep 2008 14:28:53 -0000
Mailing-List: contact carolyn93@example.net; run by ezmlm
Precedence: bulk
list-help: <mailto:carolyn93@example.net>
list-unsubscribe: <mailto:carolyn93@example.net>
List-Post: <mailto:carolyn93@example.net>
Reply-To: carolyn93@example.net
List-Id: <docs.httpd.apache.org>
Delivered-To: mailing list carolyn93@example.net
Received: (qmail 17405 invoked by uid 99); 29 Sep 2008 14:28:53 -0000
Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Sep 2008 07:28:53 -0700
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [83.161.120.155] (HELO smtp4.tech.numericable.fr) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Sep 2008 14:27:51 +0000
Received: from [83.161.120.155] (ip-90.net-82-216-215.roubaix.rev.numericable.fr [83.161.120.155])
	by smtp4.tech.numericable.fr (Postfix) with ESMTP id 5334D12A809
	for <carolyn93@example.net>; Mon, 29 Sep 2008 16:28:20 +0200 (CEST)
Message-ID: <carolyn93@example.net>
Date: Mon, 29 Sep 2008 16:28:20 +0200
From: Lucien GENTIS <carolyn93@example.net>
User-Agent: IceDove 83.161.120.155eol (X11/20080724)
MIME-Version: 1.0
To:  carolyn93@example.net
Subject: help for translation
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Hello to all,

File trunk/manual/lod/core.xml - line 2298 about FollowSymLinks option.

Could someone explain this sentence :

"Omitting this option should not be considered a security restriction, 
since symlink testing is subject to race conditions that make it 
circumventable.

Thanks

Lucien

---------------------------------------------------------------------
To unsubscribe, e-mail: carolyn93@example.net
For additional commands, e-mail: carolyn93@example.net


From carolyn93@example.net Wed Oct 01 00:00:08 2008
Return-Path: <carolyn93@example.net>
Delivered-To: carolyn93@example.net
Received: (qmail 72393 invoked from network); 1 Oct 2008 00:00:05 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155)
  by minotaur.apache.org with SMTP; 1 Oct 2008 00:00:05 -0000
Received: (qmail 11253 invoked by uid 500); 1 Oct 2008 00:00:03 -0000
Delivered-To: carolyn93@example.net
Received: (qmail 11215 invoked by uid 500); 1 Oct 2008 00:00:03 -0000
Mailing-List: contact carolyn93@example.net; run by ezmlm
Precedence: bulk
list-help: <mailto:carolyn93@example.net>
list-unsubscribe: <mailto:carolyn93@example.net>
List-Post: <mailto:carolyn93@example.net>
Reply-To: carolyn93@example.net
List-Id: <docs.httpd.apache.org>
Delivered-To: mailing list carolyn93@example.net
Received: (qmail 11204 invoked by uid 99); 1 Oct 2008 00:00:03 -0000
Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Sep 2008 17:00:03 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of carolyn93@example.net designates 83.161.120.155 as permitted sender)
Received: from [83.161.120.155] (HELO mail.lucid.net.au) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Sep 2008 23:59:01 +0000
Received: from [83.161.120.155] (winNTaint.lucid.net.au [83.161.120.155])
	by mail.lucid.net.au (Postfix) with ESMTP id BC7CB5FAC
	for <carolyn93@example.net>; Wed,  1 Oct 2008 09:59:03 +1000 (EST)
Message-ID: <carolyn93@example.net>
Date: Wed, 01 Oct 2008 09:59:02 +1000
From: Jason Lingohr <carolyn93@example.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:83.161.120.155) Gecko/20080914 Thunderbird/83.161.120.155 Mnenhy/83.161.120.1556
MIME-Version: 1.0
To: carolyn93@example.net
Subject: Re: help for translation
References: <carolyn93@example.net>
In-Reply-To: <carolyn93@example.net>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 080930-0, 30/09/2008), Outbound message
X-Antivirus-Status: Clean
X-Virus-Checked: Checked by ClamAV on apache.org

On 30/09/2008 12:28 AM, Lucien GENTIS wrote:
> Hello to all,
>
> File trunk/manual/lod/core.xml - line 2298 about FollowSymLinks option.
>
> Could someone explain this sentence :
>
> "Omitting this option should not be considered a security restriction,
> since symlink testing is subject to race conditions that make it
> circumventable.
>

The second part reads ok to me -- buffer overrun or memory allocation
exhaustion... but the "restriction" word seems odd.

Should it perhaps be "should not be considered a security
(benefit|enhancement),..."


---------------------------------------------------------------------
To unsubscribe, e-mail: carolyn93@example.net
For additional commands, e-mail: carolyn93@example.net



{'source': 'Apache Software Foundation Public Mail Archives'}