From: "M. J. Everitt" <m.j.everitt@iee.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [warning] the bug queue has 82 bugs
Date: Sat, 06 Feb 2016 22:02:45 +0000 [thread overview]
Message-ID: <56B66D85.7090907@iee.org> (raw)
In-Reply-To: <20160206220004.EDE06580AC@linuxized.com>
On 06/02/16 22:00, Alex Alexander wrote:
> Our bug queue has 82 bugs!
>
> If you have some spare time, please help assign/sort a few bugs.
>
> To view the bug queue, click here: http://bit.ly/m8PQS5
>
> Thanks!
>
Only 82? that's not, like, 4k ... :) http://tinyurl.com/maintainer-wanted .
next prev parent reply other threads:[~2016-02-06 22:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 22:00 [gentoo-dev] [warning] the bug queue has 82 bugs Alex Alexander
2016-02-06 22:02 ` M. J. Everitt [this message]
2016-02-07 2:47 ` Jeroen Roovers
-- strict thread matches above, loose matches on Subject: below --
2016-10-12 21:00 Alex Alexander
2016-09-19 21:00 Alex Alexander
2016-07-07 21:00 Alex Alexander
2016-06-29 21:00 Alex Alexander
2016-04-11 21:00 Alex Alexander
2016-04-13 6:49 ` Austin English
2016-04-13 16:00 ` M. J. Everitt
2016-01-09 22:00 Alex Alexander
2015-11-19 22:00 Alex Alexander
2015-03-01 22:00 Alex Alexander
2012-09-03 11:00 Alex Alexander
2012-07-18 11:00 Alex Alexander
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=56B66D85.7090907@iee.org \
--to=m.j.everitt@iee.org \
--cc=gentoo-dev@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox