From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-devel <sup-devel@rubyforge.org>
Cc: Rich Lane <rlane@club.cc.cmu.edu>
Subject: Re: [sup-devel] sup for sale
Date: Thu, 07 Oct 2010 00:47:43 +0200 [thread overview]
Message-ID: <1286405107-sup-889@midna.zekjur.net> (raw)
In-Reply-To: <1285263695-sup-3656@alvh.no-ip.org>
Hi Alvaro,
Excerpts from Alvaro Herrera's message of 2010-09-23 19:46:31 +0200:
> 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.
+1.
Last commit on sup/mainline:master is from 2010-07-16, which is nearly three
months. No offense, Rich, but if you don’t have time to merge patches and/or
respond to mails either, it would be a good idea to get someone else the
permissions to help you out.
Best regards,
Michael
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-10-06 22:57 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
2010-10-06 22:47 ` Michael Stapelberg [this message]
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=1286405107-sup-889@midna.zekjur.net \
--to=michael+sup@stapelberg.de \
--cc=rlane@club.cc.cmu.edu \
--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