From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: ncursesw-sup is now ncursesw
Date: Sat, 21 Dec 2013 11:13:14 +0100 [thread overview]
Message-ID: <1387620790-sup-7431@qwerzila> (raw)
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
Hi,
we've now gotten access to the 'ncursesw' gem and I have just renamed
and pushed the latest version of our 'ncursesw-sup' there. From now this
will be our ncursesw dependency.
http://rubygems.org/gems/ncursesw
ncursesw-sup will remain untill at least we have a new release of sup,
but perhaps longer so that old versions (0.13,0.14) of sup will still work.
Cheers, Gaute
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-12-21 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 10:13 Gaute Hope [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-13 18:20 Gaute Hope
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=1387620790-sup-7431@qwerzila \
--to=eg@gaute.vetsj.com \
--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