From: Decklin Foster <decklin@red-bean.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] [Sup-announce] [ANN] Sup 0.10 released
Date: Tue, 26 Jan 2010 19:07:35 -0500 [thread overview]
Message-ID: <1264550506-sup-7174@gillespie.rupamsunyata.org> (raw)
In-Reply-To: <1264344055-sup-3295@masanjin.net>
Hey William,
Could you update the tarballs on http://rubyforge.org/frs/?group_id=2603 ?
I have 0.10.1 ready to go but I'd like to put a proper orig.tar.gz in the
Debian archive this time. Thanks.
Also, I assume from the --help text of sup-convert-ferret-index that
all I need to tell users (in our NEWS.Debian) is to run it. (I deleted my
Ferret index a while ago...)
--
things change.
decklin@red-bean.com
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-01-27 0:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 14:44 [sup-devel] " William Morgan
2010-01-24 15:59 ` [sup-talk] " Mariano Mara
2010-01-24 17:02 ` William Morgan
2010-01-24 17:30 ` William Morgan
2010-01-25 0:02 ` Mariano Mara
2010-01-25 20:14 ` William Morgan
2010-01-27 0:07 ` Decklin Foster [this message]
2010-01-27 13:51 ` [sup-talk] [Sup-announce] " 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=1264550506-sup-7174@gillespie.rupamsunyata.org \
--to=decklin@red-bean.com \
--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