coar        97/07/20 06:51:05

  Modified:    .         index.html
  Log:
        Added stuff about using <[EMAIL PROTECTED]> to add text to
        problem reports.
  
  Revision  Changes    Path
  1.7       +51 -0     apache-devsite/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /export/home/cvs/apache-devsite/index.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -C3 -r1.6 -r1.7
  *** index.html        1997/07/19 16:01:33     1.6
  --- index.html        1997/07/20 13:51:04     1.7
  ***************
  *** 129,134 ****
  --- 129,185 ----
        database is logged.  If you are a member of this list, you will
        receive a message each time a report is added or modified.
        </P>
  +     <P>
  +     There is a &quot;magic&quot; mail address associated with the bug
  +     database: <SAMP>[EMAIL PROTECTED]</SAMP>.  This address is
  +     intercepted by the bug DB software; if it recognises the syntax of
  +     the <SAMP>Subject:</SAMP> line, it will attach the message text to
  +     the appropriate PR and report the transaction to the
  +     <SAMP>apache-bugdb</SAMP> list (but <STRONG>not</STRONG> to the
  +     originator of the PR - so you need to manually add that address as a
  +     <SAMP>CC</SAMP> on your message if you want the originator to
  +     receive a copy).
  +     </P>
  +     <P>
  +     The requisite syntax for GNATS to understand the subject line is:
  +     </P>
  +     <P>
  +     <DL>
  +      <DD><SAMP>Re: <EM>component</EM>/<EM>number</EM>:</SAMP>
  +      </DD>
  +     </DL>
  +     </P>
  +     <P>
  +     So a reply to <SAMP>[EMAIL PROTECTED]</SAMP> with a subject line of
  +     &quot;<SAMP>Re: general/120: this is the synopsis</SAMP>&quot; would
  +     be attached to PR #120.  (It doesn't matter if the text following
  +     the colon actually matches the real synopsis or not.)
  +     </P>
  +     <BLOCKQUOTE>
  +      <P ALIGN="CENTER">
  +      <STRONG>Note</STRONG>
  +      </P>
  +      <P>
  +      There are some caveats about using this email method to update
  +      problem reports:
  +      </P>
  +      <P>
  +      <UL>
  +       <LI><STRONG><EM>Don't</EM></STRONG> quote excessive parts of the
  +        message in your reply unless the message wasn't already logged to
  +        the PR.  (This can happen when discussions occur in private mail
  +        and you want to log the conclusions in the database.)
  +       </LI>
  +       <LI>If you send something to <SAMP>[EMAIL PROTECTED]</SAMP> that
  +        <EM>doesn't</EM> match the required <SAMP>Subject:</SAMP> syntax,
  +        or if the component/number don't exactly match an entry in the
  +        database, the message will be entered as a new report.
  +        <EM>This</EM> can happen if the PR component is changed and you
  +        reply to a message that was sent before the change.
  +       </LI>
  +      </UL>
  +      </P>
  +     </BLOCKQUOTE>
       </LI>
       <LI><A
                HREF="mailto:[EMAIL 
PROTECTED]&body=Subscribe%20Apache-CVS%0DEnd"
  
  
  

Reply via email to