From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: PATCH: scheme-modules.texi (2)
Date: 29 Aug 2003 21:51:36 +0100 [thread overview]
Message-ID: <m3r834gpbb.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <20030829092725.T1440@netdot.net>
>>>>> "Aaron" == Aaron VanDevender <sig@netdot.net> writes:
Aaron> I found a couple of mistakes in my original scheme-modules.texi
Aaron> patch, so here is a newer version. [...]
Thanks; this looks good, but I'm not sure what to do with it because
the 1.6.x and 1.7.x versions of the manual are out of sync here.
Kevin/Marius - any idea what the current position is on resolving such
differences?
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next parent reply other threads:[~2003-08-29 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030829092725.T1440@netdot.net>
2003-08-29 20:51 ` Neil Jerram [this message]
2003-08-29 22:20 ` PATCH: scheme-modules.texi (2) Kevin Ryde
2003-08-30 19:35 ` 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=m3r834gpbb.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@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).