[m-dev.] [Mercury-Language/mercury] Segfault in only Mercury after solutions in a particular code path (#72)

[Peter Wang]

On Tue, 27 Aug 2019 10:34:07 +1000 (AEST), Julien Fischer <jfischer at opturion.com> wrote:
> 
> Hi Zoltan,
> 
> On Tue, 27 Aug 2019, Zoltan Somogyi wrote:
> 
> > On a tangentially related topic: I want to add both test cases to the suite,
> > but intend to add them under the name gh72a.m and gh72b.m. We have been
> > naming test cases bugN.m for Mantis bug N for a long time. Github bug reports
> > started much more recently, so they are going over numbers that Mantis has
> > already gone over. Naming test cases from github ghN.m will avoid clashes.
> > There is already a gh65.m in tests/valid. Any objections to using this naming
> > convention from now on?
> 
> Not from me.  We should probably switch over to github as our primary
> bug tracking system.  It is possible to export the issues data from
> github, so the copy on gibhub being the only version is no longer a
> problem.  (IIRC, that was the main reason we stayed with Mantis when
> Mercury moved to git.)

Github issues did not support attachments at the time (except for
images, I think). Attachments are supported now, restricted to certain
file extensions. I think it's acceptable.

Peter