From: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: guile-user@gnu.org
Subject: Re: Guile 1.7.1 has been released.
Date: Wed, 29 Sep 2004 16:56:13 +0200 [thread overview]
Message-ID: <ljr7ol86pe.fsf@troy.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <1096326049.5951.6.camel@bubbles> (Paul Emsley's message of "28 Sep 2004 00:00:49 +0100")
Paul Emsley <emsley@ysbl.york.ac.uk> writes:
> FYI: There seems to be a problem with snarf-guile-m4-docs (you have it
> and guile-1.7.1 doesn't?):
Yes, it snarf-guile-m4-docs is missing from the 1.7.1 tarball. This
has been fixed in CVS.
If you need a new tarball, please try a snapshot:
http://www.gnu.org/software/guile/ftp-snapshots.html
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2004-09-29 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 23:02 Guile 1.7.1 has been released Marius Vollmer
2004-08-28 21:35 ` Michael Tuexen
2004-08-29 9:23 ` Andreas Vögele
2004-09-20 22:53 ` Marius Vollmer
2004-09-27 23:00 ` Paul Emsley
2004-09-29 14:56 ` Marius Vollmer [this message]
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=ljr7ol86pe.fsf@troy.dt.e-technik.uni-dortmund.de \
--to=marius.vollmer@uni-dortmund.de \
--cc=guile-user@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).