mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Luca Barbato <lu_zero@gentoo.org>
To: musl@lists.openwall.com
Subject: Re: Please consider setting up a bug tracker?
Date: Sun, 15 Feb 2015 17:53:24 +0100	[thread overview]
Message-ID: <54E0CF04.2080909@gentoo.org> (raw)
In-Reply-To: <20150215161609.GQ23507@brightrain.aerifal.cx>

On 15/02/15 17:16, Rich Felker wrote:
> On Sun, Feb 15, 2015 at 05:22:32PM +0200, Jukka Jylänki wrote:
>> Hi,
>>
>> I just recently registered to the musl mailing list to report a bug, since
>> the FAQ here http://www.musl-libc.org/faq.html mentioned that there is no
>> separate tracker to report bugs to.
>>
>> Afterwards, I now realize that this was a bad idea, since the sheer amount
>> of uninteresting emails that I began getting make it difficult to filter
>> out the discussion around musl from the potential discussion to the bug I
>> reported, and I find it simplest to unregister from the mailing list after
>> reporting the bug. However, this kind of "fire and forget" bug reporting
>> feels bad, and I lose the way to keep in touch with the communication
>> around the bug.
>>
>> I see that the issue of setting up a bug tracker has already been discussed
>> before here http://www.openwall.com/lists/musl/2014/09/05/1 . Has anything
>> changed with this respect?
>
> No, but I want a bug/patch tracker more than ever right now. There
> have been a lot of patches (and a few bug reports) coming in lately
> and it's hard to keep track of them all manually. So far bugzilla is
> probably the main candidate, but I also looked at a few others. I'd
> welcome input on what works well (both from a user standpoint and from
> an implementation-quality/hosting-considerations standpoint).

I tried to do a run about few months ago and so far bugzilla remains the 
best overall.

If you want to keep the mailinglist workflow you might look at patchwork 
or, once I manage to complete it, plaid.

lu


      parent reply	other threads:[~2015-02-15 16:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 15:22 Jukka Jylänki
2015-02-15 16:16 ` Rich Felker
2015-02-15 16:32   ` Jukka Jylänki
2015-02-15 17:40     ` Rich Felker
2015-02-15 16:53   ` Luca Barbato [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54E0CF04.2080909@gentoo.org \
    --to=lu_zero@gentoo.org \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).