From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org
Subject: Re: api differences between 1.4 and 1.6
Date: 15 Mar 2002 01:13:55 +0100 [thread overview]
Message-ID: <878z8uwuv0.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m3r8mq3kun.fsf@laruns.ossau.uklinux.net>
Neil Jerram <neil@ossau.uklinux.net> writes:
> As a purely pragmatic approach, therefore, I'd like to progressively
> reduce the differences between 1.6.x and 1.8 documentation by
> backporting the changes that are equally applicable to 1.6.x. A
> side effect of this will be that the 1.6.x documentation becomes
> more complete, even though my efforts will be (as they have been for
> some time) focussed on 1.8.
Sounds good to me!
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
parent reply other threads:[~2002-03-15 0:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <m3r8mq3kun.fsf@laruns.ossau.uklinux.net>]
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=878z8uwuv0.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--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).