From: Tom Lord <lord@regexps.com>
Subject: Re: 1.5.6 Release Needs More Eyes
Date: Sun, 17 Mar 2002 23:23:15 -0800 (PST) [thread overview]
Message-ID: <200203180723.XAA16900@morrowfield.home> (raw)
In-Reply-To: <200203180440.UAA16371@morrowfield.home> (message from Tom Lord on Sun, 17 Mar 2002 20:40:36 -0800 (PST))
From: Tom Lord <lord@regexps.com>
From: Evan Prodromou <evan@glug.org>
Umm, so, the Freshmeat page [...]
I just did a release notification on Freshmeat for 1.5.6, but this
should probably be a standard part of making new releases, no?
Yes, please. Freshmeat status is easy to keep up to date (less than
one hour of work per update). It's pretty well indexed and collects a
lot of useful information in their standard classifications. It's the
first place some of us search whenever we need some component. It's
the library catalog.
I should also add: Freshmeat listings get duplicated and emailed out
all over the place. Lot's of people are apparently like me and scan
the new listings frequently to keep up with what's going on. It's a
really, neat thing.
-t
(Of course I'm still all pissed about #f/nil, shared substrings,
conservative GC, obnoxious "triumverant" comments, etc. and Guile just
plain sucks, in my book, but since that isn't a universal opinion --
by all means, please keep the FM listing up-to-date.)
(Oh, ok, if I must: :-) ... whatever that means.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-18 7:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-17 23:34 1.5.6 Release Needs More Eyes Evan Prodromou
2002-03-18 3:40 ` Rob Browning
2002-03-18 3:56 ` Evan Prodromou
2002-03-18 4:40 ` Tom Lord
2002-03-18 7:23 ` Tom Lord [this message]
2002-03-18 18:47 ` Evan Prodromou
2002-03-18 20:55 ` Neil Jerram
2002-03-18 21:33 ` Evan Prodromou
2002-03-18 22:00 ` Rob Browning
2002-03-18 21:19 ` Tom Lord
2002-03-29 4:41 ` Thien-Thi Nguyen
2002-03-18 20:41 ` Neil Jerram
2002-03-18 18:34 ` Evan Prodromou
2002-03-18 19:12 ` Rob Browning
2002-03-20 22:00 ` Marius Vollmer
2002-03-21 18:06 ` Rob Browning
2002-04-03 6:12 ` Thien-Thi Nguyen
2002-04-03 6:36 ` Rob Browning
2002-04-03 5:20 ` Thien-Thi Nguyen
2002-04-03 6:38 ` Rob Browning
2002-04-03 9:44 ` Thien-Thi Nguyen
2002-04-03 10:25 ` Thien-Thi Nguyen
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200203180723.XAA16900@morrowfield.home \
--to=lord@regexps.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).