Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: William Morgan <wmorgan-sup@masanjin.net>
To: Sup-talk mailing list <sup-talk@rubyforge.org>
Subject: [sup-talk] new list: sup-devel
Date: Tue, 03 Nov 2009 11:00:39 -0800	[thread overview]
Message-ID: <1257272092-sup-9031@masanjin.net> (raw)

Hi all,

I've created a new list for Sup developer discussion. This has been
requested a couple times, and I finally think the traffic level warrants
it.

If you're interested, please subscribe here:

  http://rubyforge.org/mailman/listinfo/sup-devel

I'm not going to be too strict about it, and we can finish up the bug
tracker conversation here, but I would like sup-talk to eventually be a
place for user questions and discussions, and for future conversations
about code, bugs, bug trackers, etc to talk place over there.

I'm going to change the bug report email address in 0.9.1 to sup-devel
as well. (And hopefully to a URL in 0.10.)
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


                 reply	other threads:[~2009-11-03 19:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1257272092-sup-9031@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