Changes between Version 4 and Version 5 of ReportBugs

Timestamp:

Jul 30, 2007, 5:44:25 PM (17 years ago)

Author:

Nicolas

Comment:

Server-relative links, and InterWiki links for mailing lists.

ReportBugs

@@ -16 +16 @@
 When BOINC does something wrong, one or more of these files often contain information that allows us (i.e. BOINC developers) to easily find and fix the problem.
 == Reporting hard bugs ==
-Report hard bugs by email, either to the [http://www.ssl.berkeley.edu/mailman/listinfo/boinc_alpha boinc_alpha] email list or directly to [ProjectPeople David and Rom]. '''Note: when you post to boinc_alpha, attachments are stripped from your email; include text inline rather than as attachments. There's a 200KB limit.''' Your bug report should include:
+Report hard bugs by email, either to the [mlist:boinc_alpha boinc_alpha] email list or directly to [ProjectPeople David and Rom]. '''Note: when you post to boinc_alpha, attachments are stripped from your email; include text inline rather than as attachments. There's a 200KB limit.''' Your bug report should include:
  * The context: what platform, what version of BOINC, anything else that might be relevant.
  * What sequence of actions caused the problem.
@@ -27 +27 @@
 If the Manager suddenly does blank and says 'not connected', it's almost certainly because the core client has crashed. You can verify this by running the Windows Task Manager (ctrl-alt-del) and checking that there's no process named 'boinc.exe'.
 
-Each crash appends an entry to the crash-report file (stderrdae.txt for the core client). Here's [http://boinc.berkeley.edu/stderrdae.txt an example of such an entry]. It has a long list of DLLs in use at the time of the crash, followed by several 'stack traces' showing where the various threads were executing.
+Each crash appends an entry to the crash-report file (stderrdae.txt for the core client). Here's [/stderrdae.txt an example of such an entry]. It has a long list of DLLs in use at the time of the crash, followed by several 'stack traces' showing where the various threads were executing.
 
 Your bug report email should include the most recent entry from your crash-report file. Please edit the file to remove old entries, so that we don't get confused by them.
@@ -45 +45 @@
 }}}
 
-A typical message log is shown [http://boinc.berkeley.edu/stdoutdae.txt here]. Note that each line contains
+A typical message log is shown [/stdoutdae.txt here]. Note that each line contains
 
  * The date and time when the message was written