[m-rev.] for review: BUGS file rewrite

[Julien Fischer]

On Thu, 27 May 2010, Ian MacLarty wrote:

>> +Alternatively, you may email bug reports to
>> mercury-bugs at csse.unimelb.edu.au.
>> +If you are reporting more than one bug, please use separate emails for each
>> +bug.  (If it's something that only shows up in multi-module programs, send
>> +a shar archive or uuencoded tar archive including your source files.)
>> +
>
> It might be worth mentioning that the mercury-bugs list gets a lot of
> spam, so it's possible that reports sent to that list may be
> overlooked and that the preferred way to report bugs is via mantis.

In practice, it doesn't seem to have been much of a problem.

>> +Please include the following information in your bug report:
>> +
>> +  * the version of Mercury;
>> +  * the system type;
>> +  * a complete source file that demonstrates the problem;
>> +  * the command line flags with which the Mercury compiler was invoked;
>> +  * the name and version of the C compiler that you are using;
>> +
>> +For bugs that involve the Erlang or Java backends, include the name and
>> version
>> +of the Erlang or Java implementation that you are using.
>> +
>> +Please try to ensure that bug report contains all the information that we
>> need to
>> +be able to reproduce the problem.  Make sure that all bug reports are fully
>> +self-contained.
>> +
>> +The bug tracking system contains a current list of known outstanding bugs.
>> +Some other problems related to using Mercury specific operating systems are
>
> ...Mercury *on* specific...

Fixed.

Cheers,
Julien.