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

Zoltan Somogyi zoltan.somogyi at runbox.com
Tue Aug 27 11:55:20 AEST 2019



On Tue, 27 Aug 2019 10:34:07 +1000 (AEST), Julien Fischer <jfischer at opturion.com> wrote:
> 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.)

I find Mantis's user interface to be much easier to use than Github's for this,
so I would prefer to keep using Mantis as our primary bug database. Since
people can report issues via Github, they will, let's not encourage its use for this.

Zoltan.


More information about the developers mailing list