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. <div class="gmail_quote">On 16 Jan 2013 12:13, "Paul Bone" <<a href="mailto:paul@bone.id.au">paul@bone.id.au</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> On Wed, Jan 16, 2013 at 11:42:13AM +1100, Peter Wang wrote: > On Tue, 15 Jan 2013 16:40:10 -0700, Michael Hendricks <<a href="mailto:michael@ndrix.org">michael@ndrix.org</a>> wrote: > > On Tue, Jan 15, 2013 at 2:41 PM, Paul Bone <<a href="mailto:paul@bone.id.au">paul@bone.id.au</a>> 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 <a href="http://www.bone.id.au" target="_blank">http://www.bone.id.au</a> </blockquote></div>