Index: sf-faq.html
===================================================================
RCS file: /cvsroot/python/python/nondist/sf-html/sf-faq.html,v
retrieving revision 1.15
diff -c -r1.15 sf-faq.html
*** sf-faq.html	2000/08/25 07:55:48	1.15
--- sf-faq.html	2000/11/01 14:33:50
***************
*** 57,63 ****
  <h2><a href="#bugs">6. Bug Reporting</a></h2>
  <ol>
    <li><a href="#b1">Where can I submit/view bugs for Python?</a></li>
!   <li><a href="#b2">How do I use jitterbug?</a></li>
  </ol>
  
  <h2><a href="#appendix">A. Appendix</a></h2>
--- 57,63 ----
  <h2><a href="#bugs">6. Bug Reporting</a></h2>
  <ol>
    <li><a href="#b1">Where can I submit/view bugs for Python?</a></li>
!   <li><a href="#b2">How do I use the sourceforge bug manager?</a></li>
  </ol>
  
  <h2><a href="#appendix">A. Appendix</a></h2>
***************
*** 446,472 ****
  <h4>Q: Where can I submit/view bugs for Python?</h4>
  
  <h4>A:</h4>
! As of now [25-Jul-200] the Python project does not use SourceForge's bug
! tracking facility. This may change when there is a way to import the existing
! jitterbug database. The jitterbug database can be accessed through the
! following interface:
  
- <blockquote>
-   <tt><a
-   href="http://www.python.org/python-bugs">http://www.python.org/python-bugs</a></tt></blockquote>
- 
  <h3><a name="b1" id="b1"></a>6.1.:</h3>
  
! <h4>Q: How do I use jitterbug?</h4>
  
  <h4>A:</h4>
! To get the list of open bugs click on <tt>open</tt> (hidden between the second
! last and the last horizontal ruler).
  
! <p>To get a list of the bugs which are related to some area, enter an
! appropriate regular expression and press "Select Messages". Then select
! <tt>open</tt> (or whatever category you would like to view) as described
! above.</p>
  
  <h1><a name="appendix" id="appendix"></a>A. Appendix</h1>
  
--- 446,466 ----
  <h4>Q: Where can I submit/view bugs for Python?</h4>
  
  <h4>A:</h4>
! The Python project uses SourceForge's bug
! tracking facility. Go to 
! <a href="http://sourceforge.net/bugs/?group_id=5470">http://sourceforge.net/bugs/?group_id=5470</a> for all bug management needs.
  
  <h3><a name="b1" id="b1"></a>6.1.:</h3>
  
! <h4>Q: How do I use the sourceforge bug manager?</h4>
  
  <h4>A:</h4>
! By default, you will see the list of all Open bugs. You can change
! which bugs you're viewing by selecting the assigned_to/status/area/type
! select boxs.
  
! <p>To submit a bug, use the "Submit a Bug" link, near the top of the page.
! </p>
  
  <h1><a name="appendix" id="appendix"></a>A. Appendix</h1>
  
***************
*** 600,616 ****
      mailing list address; this address should no longer be used for patch
      submission. The patch manager is for <b>patches</b> only; if you have a
      problem or suggestion but don't know how to write the code for it, use the
!     <a href="http://www.python.org/search/search_bugs.html">Python Bugs
!     List</a> instead. The bugs list is searchable; if you have a problem and
      you're not sure if it has been reported or fixed already, this is the
      first place to look. (There used to be a separate TODO list; we now prefer
      that you use the bugs list for suggestions and requests too.)</li>
    <li style="list-style: none"><b>Submit documentation patches the same
      way.</b> When adding the patch, be sure to set the "<b>Category</b>" field
      to "<b>documentation</b>". For documentation errors without patches,
!     please use the <a
!     href="http://www.python.org/search/search_bugs.html">Python Bugs List</a>
!     instead.</li>
    <li>We like context diffs. We grudgingly accept unified diffs. <b>Straight
      ("ed-style") diffs are right out!</b> If you don't know how to generate
      context diffs, you're probably not qualified to produce high-quality
--- 594,608 ----
      mailing list address; this address should no longer be used for patch
      submission. The patch manager is for <b>patches</b> only; if you have a
      problem or suggestion but don't know how to write the code for it, use the
!     <a href="#b1">bug reporting mechanism</a> instead. 
!     The bugs list is searchable; if you have a problem and
      you're not sure if it has been reported or fixed already, this is the
      first place to look. (There used to be a separate TODO list; we now prefer
      that you use the bugs list for suggestions and requests too.)</li>
    <li style="list-style: none"><b>Submit documentation patches the same
      way.</b> When adding the patch, be sure to set the "<b>Category</b>" field
      to "<b>documentation</b>". For documentation errors without patches,
!     please use the <a href="b1">bug reporting mechanism</a>.</li>
    <li>We like context diffs. We grudgingly accept unified diffs. <b>Straight
      ("ed-style") diffs are right out!</b> If you don't know how to generate
      context diffs, you're probably not qualified to produce high-quality