From: Andrei Thorp <garoth@gmail.com>
To: William Morgan <wmorgan-sup@masanjin.net>, sup-talk@rubyforge.org
Subject: Re: [sup-talk] slowly catching up
Date: Thu, 5 Nov 2009 21:38:26 -0500 [thread overview]
Message-ID: <80055d7c0911051838m855262bi93d149549de2da8c@mail.gmail.com> (raw)
In-Reply-To: <1256997213-sup-2725@masanjin.net>
On Sat, Oct 31, 2009 at 9:03 AM, William Morgan
<wmorgan-sup@masanjin.net> wrote:
> Suggestions welcome.
I propose promoting Rich Lane to commiter if he's up for it and
doesn't have access yet. From what I can tell, he's done a terrific
job thus far, and has a lot of experience with Sup.
-AT
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-11-06 2:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 14:03 William Morgan
2009-11-02 7:29 ` Tero Tilus
2009-11-03 18:14 ` William Morgan
2009-11-06 2:38 ` Andrei Thorp [this message]
2009-11-06 4:13 ` Rich Lane
2009-11-06 13:47 ` William Morgan
2009-11-07 7:09 ` Rich Lane
2009-11-07 9:34 ` Tero Tilus
2009-11-07 16:56 ` 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=80055d7c0911051838m855262bi93d149549de2da8c@mail.gmail.com \
--to=garoth@gmail.com \
--cc=sup-talk@rubyforge.org \
--cc=wmorgan-sup@masanjin.net \
/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