From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org, Aaron VanDevender <sig@netdot.net>
Subject: Re: PATCH: scheme-modules.texi (2)
Date: Sat, 30 Aug 2003 08:20:01 +1000 [thread overview]
Message-ID: <87znhs2jji.fsf@zip.com.au> (raw)
In-Reply-To: <m3r834gpbb.fsf@laruns.ossau.uklinux.net> (Neil Jerram's message of "29 Aug 2003 21:51:36 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
>
> Kevin/Marius - any idea what the current position is on resolving such
> differences?
Myself I'd only been putting fixes for errors of fact into the 1.6
branch, and confining new stuff and tweaks to the head.
(I don't think I've been fiddling with scheme-modules.texi as such.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-08-29 22:20 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 ` PATCH: scheme-modules.texi (2) Neil Jerram
2003-08-29 22:20 ` Kevin Ryde [this message]
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=87znhs2jji.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@gnu.org \
--cc=sig@netdot.net \
/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).