This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Add note in lists.html about confidentiality notices



This change updates lists.html to reflect what I believe is already
existing policy, and has been previously discussed at
<http://gcc.gnu.org/ml/gcc/2002-01/msg00872.html> and the following
thread.  I put a brown paper bag over the company's name out of a
sense of shame :-(.

I also added a few <p> tags which the validator I was using
complained about.

-- 
Geoff Keating <geoffk@redhat.com>

===File ~/patches/wwwdocs-disclaimers.patch=================
Index: lists.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/lists.html,v
retrieving revision 1.76
diff -p -c -r1.76 lists.html
*** lists.html	2002/01/23 15:42:21	1.76
--- lists.html	2002/02/18 18:14:02
*************** and try to avoid cross posting a message
*** 135,140 ****
--- 135,161 ----
  
  <p>Please refrain from sending messages in HTML, RTF or similar formats.</p>
  
+ <p>Please do not include or reference confidentiality notices, like:</p>
+ <blockquote>
+ 	<p>The referring document contains privileged and confidential
+ 	information. If you are not the intended recipient
+ 	you must not disseminate, copy or take any action
+ 	in reliance on it, and we request that you notify
+ 	<var>companyname</var> immediately.</p>
+ </blockquote>
+ <p>Such disclaimers are inappropriate for mail sent to public lists.  If
+ your company automatically adds something like this to outgoing mail,
+ and you can't convince them to stop, you might consider using a free
+ web-based e-mail account.</p>
+ 
+ <p>Notices like:</p>
+ <blockquote>
+ 	<p>Any views expressed in this message are those of the
+ 	individual sender, except where they are specifically stated
+ 	to be the views of <var>companyname</var>.</p>
+ </blockquote>
+ <p>are acceptable, although they are redundant; unless explicitly stated,
+ it's assumed that no-one on these lists means to speak for their company.</p>
  
  <h2>Archives</h2>
  
*************** lists via this form:</p>
*** 162,168 ****
  
  <blockquote>
  <form method="get" action="http://gcc.gnu.org/cgi-bin/ml-request";>
!   Mailing list: 
    <select name="listname">
     <option value="gcc-announce">gcc-announce</option>
     <option value="gcc">gcc</option>
--- 183,189 ----
  
  <blockquote>
  <form method="get" action="http://gcc.gnu.org/cgi-bin/ml-request";>
!   <p>Mailing list: 
    <select name="listname">
     <option value="gcc-announce">gcc-announce</option>
     <option value="gcc">gcc</option>
*************** lists via this form:</p>
*** 193,199 ****
      <option value="unsubscribe">unsubscribe</option>
    </select>
    &nbsp;
!  <input type="submit" name="submit" value="Process that!" />
  </form>
  </blockquote>
  
--- 214,220 ----
      <option value="unsubscribe">unsubscribe</option>
    </select>
    &nbsp;
!  <input type="submit" name="submit" value="Process that!" /></p>
  </form>
  </blockquote>
  
*************** List-Archive, etc.).</p>
*** 218,237 ****
  <p>For example, the following procmail rule will sort all mail from
  our lists into a single folder named INLIST.gcc:</p>
  
! <blockquote><code>
  :0<br />
  * ^Sender: .*-owner@gcc.gnu.org<br />
  INLIST.gcc<br />
! </code></blockquote>
  
  <p>To filter duplicate messages due to cross-posts to multiple lists, you
  can use the following recipe (Use at your own risk!):</p>
  
! <blockquote><code>
  :0 Wh: msgid.lock<br />
  * ^Sender: .*-owner@gcc.gnu.org<br />
  | formail -D 8192 msgid.cache
! </code></blockquote>
  
  <h2>Help</h2>
  
--- 239,258 ----
  <p>For example, the following procmail rule will sort all mail from
  our lists into a single folder named INLIST.gcc:</p>
  
! <blockquote><p><code>
  :0<br />
  * ^Sender: .*-owner@gcc.gnu.org<br />
  INLIST.gcc<br />
! </code></p></blockquote>
  
  <p>To filter duplicate messages due to cross-posts to multiple lists, you
  can use the following recipe (Use at your own risk!):</p>
  
! <blockquote><p><code>
  :0 Wh: msgid.lock<br />
  * ^Sender: .*-owner@gcc.gnu.org<br />
  | formail -D 8192 msgid.cache
! </code></p></blockquote>
  
  <h2>Help</h2>
  
============================================================


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]