From: Neil Jerram <neil@ossau.uklinux.net>
To: Guile Development <guile-devel@gnu.org>
Subject: Re: complex number reader bug?
Date: Wed, 01 Jul 2009 20:07:24 +0100 [thread overview]
Message-ID: <873a9g1atv.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <87prcljkp4.fsf@arudy.ossau.uklinux.net> (Neil Jerram's message of "Wed\, 01 Jul 2009 01\:44\:39 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
> Below is a patch for review. It was an interesting problem, as I
> haven't gone very far into Guile's number handling code before.
I've pushed this to master too, and that raises two points about the
organization of master's NEWS.
Firstly, now that 1.9.0 has been released, I'm not sure it makes sense
for 1.9.x NEWS to refer to `Changes in 1.8.x' for x >= 7. It seems
more natural for NEWS to refer to actual releases in chronological
order, so I think the right thing would be for
- `Changes in 1.9.0 (changes since the 1.8.x series)' to be renamed
`Changes in 1.9.0 (changes since 1.8.6)'
- all of the `Changes in 1.8.7 (since 1.8.6)' items to be merged into
`Changes in 1.9.0 (changes since 1.8.6)'.
Secondly, are we going to retain the distinctions between the 1.9.x
releases, once 2.0 is released? I would guess yes, because I see no
point in discarding information that might be useful.
If so, note that it's worth taking care to get the right place when
adding a missing NEWS item for something that was already in a
previous release - which I think is a good thing to do, so that the
1.8.x - 2.0 NEWS is as complete as possible. I.e. if we now find
something that should have been in the NEWS for 1.9.0, we
retrospectively insert it into the `Changes in 1.9.0 (changes since
1.8.6)' section, and not into `Changes in 1.9.1 (changes since
1.9.0)'.
Does that all sound right?
(If it does, I will need to move the NEWS for this complex number fix
to `Changes in 1.9.1 (changes since 1.9.0)'.)
Regards,
Neil
next parent reply other threads:[~2009-07-01 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081018194523.M24362@ccrma.Stanford.EDU>
[not found] ` <87prcljkp4.fsf@arudy.ossau.uklinux.net>
2009-07-01 19:07 ` Neil Jerram [this message]
2009-07-01 22:30 ` complex number reader bug? Ludovic Courtès
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=873a9g1atv.fsf@arudy.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).