From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] sup for sale
Date: Thu, 23 Sep 2010 13:46:31 -0400 [thread overview]
Message-ID: <1285263695-sup-3656@alvh.no-ip.org> (raw)
In-Reply-To: <1285241702-sup-3344@dolk>
Excerpts from Gaute Hope's message of jue sep 23 07:50:23 -0400 2010:
> First; thanks to both William and Rich for the great work on sup. I'm
> using it full time now since I don't-really-know-anymore, there are
> occasional bugs and more than a few problems with ruby 1.9 - but things
> are starting to get along. Awesome work!
Seconded!
> I just want to support the point of Christian Dietrich of perhaps adding
> another maintainer/committer to be able to take some of the load when
> Rich might be busy or gone for a while. I agree that it can be
> de-motivating to contribute when you see the patches pile up, I imagine
> it must be harder to go through the backlog as well. Still think Rich is
> the man for the job thou, so he's the boss!
I just want to add that it's a bit discouraging to see that the master
branch doesn't move a bit for a long time. So it would be very good for
morale of us poor users to have someone else pushing patches, even if
it's just the minor bugfixes that we see pop up on the mailing lists.
(I don't have a lot to offer myself in term of patches, but I do have a
couple of very minor fixes sitting in my private tree just because it
seems rather pointless to send them along right now.)
--
Álvaro Herrera <alvherre@alvh.no-ip.org>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-09-23 22:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 14:51 William Morgan
2010-02-25 15:32 ` Christian Dietrich
2010-09-23 11:50 ` Gaute Hope
2010-09-23 17:46 ` Alvaro Herrera [this message]
2010-10-06 22:47 ` Michael Stapelberg
2010-10-07 3:08 ` Rich Lane
2010-02-25 20:04 ` Tero Tilus
2010-02-25 21:55 ` Rich Lane
2010-02-25 23:26 ` William Morgan
2010-02-26 14:05 ` William Morgan
2010-02-26 16:07 ` Tero Tilus
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=1285263695-sup-3656@alvh.no-ip.org \
--to=alvherre@alvh.no-ip.org \
--cc=sup-devel@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