From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: on the importance of names
Date: Tue, 31 May 2011 22:38:43 +0200 [thread overview]
Message-ID: <m3aae2obak.fsf@unquote.localdomain> (raw)
In-Reply-To: <87pqp73aar.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 31 Mar 2011 11:32:12 +0200")
Hi!
On Thu 31 Mar 2011 11:32, ludo@gnu.org (Ludovic Courtès) writes:
> Andy Wingo <wingo@pobox.com> writes:
>
>> It would be nice to add it in 2.0.x, as it's a compatible change.
>
> OK, sounds good! I guess you’ll have to add the explanation of why the
> name’s so great to the manual. :-)
Done. Here's the initial text:
4.5 Using Guile Tools
=====================
Guile also comes with a growing number of command-line utilities: a
compiler, a disassembler, some module inspectors, and in the future, a
system to install Guile packages from the internet. These tools may be
invoked using the `guild' program.
$ guild compile -o foo.go foo.scm
wrote `foo.go'
This program used to be called `guile-tools', and for backward
compatibility it still may be called as such. However we changed the
name to `guild', not only because it is pleasantly shorter and easier
to read, but also because this tool will serve to bind Guile wizards
together, by allowing hackers to share code with each other using a
CPAN-like system.
*Note Compilation::, for more on `guild compile'.
A complete list of guild scripts can be had by invoking `guild
list', or simply `guild'.
Please fix it to say something different if you want :)
>> But, there's no need for it to hold back a 2.0.1 release; there's a
>> lot of NEWS to write up there, and we should get that out soonish.
>
> Agreed.
>
> How about pushing the release by the end of next week (Apr. 10th)?
FWIW I have a draft of NEWS I'd like to push soonish. Perhaps we can
release this week.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-05-31 20:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 11:36 proposal: enhance and rename guile-tools Andy Wingo
2011-03-20 23:16 ` Ludovic Courtès
2011-03-21 8:27 ` Andy Wingo
2011-03-21 11:51 ` nalaginrut
2011-03-21 11:58 ` nalaginrut
2011-03-21 12:16 ` Barry Fishman
2011-03-21 14:10 ` Neil Jerram
2011-03-21 19:28 ` Andy Wingo
2011-03-21 21:50 ` Neil Jerram
2011-03-30 10:51 ` Andy Wingo
2011-03-30 18:27 ` Neil Jerram
2011-03-21 16:32 ` dsmich
2011-03-21 15:12 ` David Pirotte
2011-03-21 15:00 ` Jose A. Ortega Ruiz
2011-03-30 11:08 ` on the importance of names (was: proposal: enhance and rename guile-tools) Andy Wingo
2011-03-30 13:11 ` Noah Lavine
2011-03-30 13:15 ` nalaginrut
2011-03-30 15:52 ` on the importance of names Ludovic Courtès
2011-03-30 16:25 ` Andy Wingo
2011-03-31 9:32 ` Ludovic Courtès
2011-05-31 20:38 ` Andy Wingo [this message]
2011-05-31 21:55 ` Ludovic Courtès
2011-03-30 18:11 ` Neil Jerram
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=m3aae2obak.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).