From: Kevin Ryde <user42@zip.com.au>
Subject: merge from 1.8 branch
Date: Tue, 10 Oct 2006 10:15:09 +1000 [thread overview]
Message-ID: <87odslqb5e.fsf@zip.com.au> (raw)
I did another dreaded merge from 1.8 onto the head, mostly bits and
pieces by me. As usual the diff between the two can be seen (from a
head checkout dir) with
cvs diff -r branch_release-1-8 -r HEAD
It's a shame the diff is growing.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2006-10-10 0:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 0:15 Kevin Ryde [this message]
2006-10-10 19:32 ` merge from 1.8 branch Neil Jerram
2006-10-11 19:57 ` Kevin Ryde
2006-10-20 20:47 ` Neil Jerram
2006-10-21 13:17 ` Ludovic Courtès
2006-10-22 17:50 ` Rob Browning
2006-10-25 18:49 ` Neil Jerram
2006-10-25 19:22 ` Rob Browning
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=87odslqb5e.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).