From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel mailing list <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] sup for sale
Date: Thu, 25 Feb 2010 18:26:54 -0500 [thread overview]
Message-ID: <1267140372-sup-1058@masanjin.net> (raw)
In-Reply-To: <1267132217-sup-2260@zyrg.net>
Reformatted excerpts from Rich Lane's message of 2010-02-25:
> I'm willing to do it. I've been working on other projects lately, but
> I can make time for Sup. I created accounts (rlane) at gitorious and
> rubyforge.
Awesome. I have added you to RubyForge and Gitorious. For Gemcutter, I
think I will need the secret email address that you signed up with to
add you as someone who can push new releases.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-02-25 23:39 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
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 [this message]
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=1267140372-sup-1058@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--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