Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: 5srmspw02@sneakemail.com (Sukant Hajra)
Subject: [sup-talk] How's STS coming?
Date: Thu, 2 Oct 2008 17:19:25 +0000 (UTC)	[thread overview]
Message-ID: <slrngea0kr.sbb.0osz0s302@hole.internal.mydonutshop.org> (raw)

Hi William,

I just tried to post a longer message about how STS was coming, but I'm not
sure it sent.  If it did send, I didn't want repeat myself here.

If it didn't send, it really wan't saying much. . . just along the lines of

    - How's STS coming?

    - If it's not soon to be released, do you think we can at least see the
      tree (I'm just curious to see it)

    - I'm eagerly awaiting, and if STS is stalled, I'm thinking about other
      ways to manage mail/NNTP/RSS, but I don't want to waste my time if STS is
      around the corner.

Thanks for all your hard work,
Sukant



             reply	other threads:[~2008-10-02 17:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02 17:19 Sukant Hajra [this message]
2008-10-02 21:21 ` Marcus Williams
2008-10-02 22:01 ` William Morgan
2008-10-07 19:00   ` William Morgan
2008-10-13 18:14     ` 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=slrngea0kr.sbb.0osz0s302@hole.internal.mydonutshop.org \
    --to=5srmspw02@sneakemail.com \
    /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