From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] [PATCH] minor nits in exception apology message
Date: Sun, 01 Nov 2009 06:39:25 -0800 [thread overview]
Message-ID: <1257086191-sup-1136@masanjin.net> (raw)
In-Reply-To: <1256987483-sup-338@tilus.net>
Reformatted excerpts from Tero Tilus's message of 2009-10-31:
> How about setting up a loose team which would handle the incoming bug
> reports (for you), track/sort all of them and fix what they feel like
> fixing and maybe upon request/occasionally report somewhere the
> current status (how many minors and majors open).
As far as I'm concerned, that would be great. I'm open to suggestions
about how to organize this. At this point I'm pretty convinced I will
never actually like a bug tracker, and I don't have the energy to write
another one, so for someone else to take the initiative would be
awesome.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-11-01 14:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 17:14 Jon Dugan
2009-10-28 20:05 ` Nicolas Pouillard
2009-10-28 20:22 ` Jon Dugan
2009-10-29 10:29 ` Nicolas Pouillard
2009-10-30 21:53 ` William Morgan
2009-10-31 11:28 ` Tero Tilus
2009-11-01 14:39 ` William Morgan [this message]
2009-11-01 15:24 ` Nicolas Pouillard
2009-11-01 16:19 ` William Morgan
2009-11-01 16:48 ` Nicolas Pouillard
2009-11-01 17:30 ` William Morgan
2009-11-01 17:49 ` Nicolas Pouillard
2009-11-01 20:30 ` rick.tessner
2009-11-02 7:19 ` Tero Tilus
2009-11-02 15:07 ` William Morgan
2009-11-02 7:25 ` [sup-talk] Sup Issues Task Force (SITF) Tero Tilus
2009-11-02 9:14 ` Israel Herraiz
2009-11-02 15:08 ` William Morgan
2009-11-03 1:45 ` Tero Tilus
[not found] ` <1256940689-sup-888@arrakis.es.net>
2009-11-01 14:45 ` [sup-talk] [PATCH] minor nits in exception apology message William Morgan
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=1257086191-sup-1136@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@rubyforge.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