From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: Branching for 1.8 on 2006-02-05
Date: Sat, 04 Feb 2006 10:49:39 +1100 [thread overview]
Message-ID: <87ek2k80ks.fsf@zip.com.au> (raw)
In-Reply-To: 87fyn8xtj3.fsf@zagadka.de
Marius Vollmer <mvo@zagadka.de> writes:
>
> I want to branch next weekend, on Sunday, 5. Feb. Before that, the
> following things should be settled in trunk,
There's also an error
Non-pair accessed with SCM_C[AD]R: `#<<class> <foo> b7a0eae0>'
thrown up by goops.test under debug cell acesses. Dunno what it means.
> (What we have in the 1.8 branch is not immediately the 1.8.0 release,
> but should be very close.)
Do you really want to branch at all?
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-02-03 23:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 15:26 Branching for 1.8 on 2006-02-05 Marius Vollmer
2006-01-29 9:13 ` Neil Jerram
2006-01-29 12:45 ` Han-Wen Nienhuys
2006-02-03 23:49 ` Kevin Ryde [this message]
2006-02-04 19:38 ` Rob Browning
2006-02-05 19:02 ` Marius Vollmer
2006-02-05 20:30 ` Rob Browning
2006-02-06 9:25 ` Ludovic Courtès
2006-02-07 0:18 ` Marius Vollmer
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=87ek2k80ks.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).