[m-dev.] Hosting.

[Matt Giuca]

Also can't have private bug reports, which are important for security
vulnerability disclosures.

It's a shame, because it is a really nice issue tracker. I like that it
supports Markdown.
On 16 Jan 2013 12:13, "Paul Bone" <paul at bone.id.au> wrote:

> On Wed, Jan 16, 2013 at 11:42:13AM +1100, Peter Wang wrote:
> > On Tue, 15 Jan 2013 16:40:10 -0700, Michael Hendricks <michael at ndrix.org>
> wrote:
> > > On Tue, Jan 15, 2013 at 2:41 PM, Paul Bone <paul at bone.id.au> wrote:
> > >
> > > > If we wanted to we could use a static system such as this and use
> github or
> > > > another provider's issue tracker.
> > >
> > >
> > > I recommend using GitHub's issue tracker regardless what's decided
> about
> > > hosting.  It's really nice to automatically close issues from a commit
> > > message ("Closes #1234") and have links from the issue tracker back to
> > > relevant commits.  As one who dislikes server management, it's also
> nice to
> > > have GitHub take care of that part too :-)
> >
> > Can't attach files. Useless.
> >
>
> I agree with Peter here.
>
> If you've a bug and want to submit a small program that exibits the bug.
> you
> shouldn't need to download the entire Mercury repository and work out where
> in tests/ your fix belongs.  Or maybe this is what gist is for?  Anyway
> it'd
> be nice if that were obvious from the github interface.
>
> We should submit a feature request.
>
>
> --
> Paul Bone
> http://www.bone.id.au
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurylang.org/archives/developers/attachments/20130116/904e380e/attachment.html>